Wsrep position not updated in InnoDB after certification failures (#1432)

A certification failure followed by a clean shutdown would cause an
inconsistency between the sequence number stored in innodb and the
sequence number stored in provider.
This happened both in the case of local certification failure, and in
the case where dummy writeset is applied.
The fix consists of:
- updating wsrep position after dummy writeset is delivered in
 `Wsrep_high_priority_service::log_dummy_write_set()`
- updating wsrep position while releasing commit order in wsrep-lib
 side

Added two tests which stress the situation where a server is shutdown
after a certification failure.

1 files changed, 6 insertions, 0 deletions

diff --git a/sql/wsrep_server_service.cc b/sql/wsrep_server_service.cc
index aa288e67420..d0a9b54ac1b 100644
--- a/sql/wsrep_server_service.cc
+++ b/sql/wsrep_server_service.cc
@@ -302,6 +302,12 @@ wsrep::gtid Wsrep_server_service::get_position(wsrep::client_service&)
   return wsrep_get_SE_checkpoint();
 }
 
+void Wsrep_server_service::set_position(wsrep::client_service&,
+                                        const wsrep::gtid& gtid)
+{
+  wsrep_set_SE_checkpoint(gtid);
+}
+
 void Wsrep_server_service::log_state_change(
   enum Wsrep_server_state::state prev_state,
   enum Wsrep_server_state::state current_state)