From 2d4b6571ecf15a4382702d26df9439bc5a1005de Mon Sep 17 00:00:00 2001 From: Daniele Sciascia Date: Tue, 14 Jan 2020 06:33:02 +0100 Subject: 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. --- wsrep-lib | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'wsrep-lib') diff --git a/wsrep-lib b/wsrep-lib index 76f7249b8df..a17b65a25f5 160000 --- a/wsrep-lib +++ b/wsrep-lib @@ -1 +1 @@ -Subproject commit 76f7249b8df209a2a3cefd7d4bbf31f6c72812f1 +Subproject commit a17b65a25f5e608ffa8e6e051930bf47ed95019a -- cgit v1.2.1