Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3.9, 10.3.11, 10.3.14, 10.3.15
-
None
-
CentOS 7, running on XenServer hypervisor.
Description
Servers went down due to failed query. I bootstrapped cluster and was unable to start the remaining nodes with the following error:
2018-10-12 20:12:15 0 [Warning] WSREP: SST position can't be set in past. Requested: 92172, Current: 3620686.
2018-10-12 20:12:15 0 [Warning] WSREP: Can't continue.
2018-10-12 20:12:15 0 [ERROR] Aborting
It says the current commit is 3620686, but it was actually 9953033. Not sure why this matters since the cluster was restarted and that number restarted.
Attachments
Issue Links
- causes
-
MDEV-33540 mariabackup --prepare: [ERROR] InnoDB: Crash recovery is broken due to insufficient innodb_log_file_size
- Closed
- is caused by
-
MDEV-15158 On commit, do not write to the TRX_SYS page
- Closed
- relates to
-
MDEV-19193 The --wsrep-new-cluster option does not reset wsrep_cluster_state_uuid and wsrep_last_committed
- Closed
-
MDEV-18177 Galera test failure on galera_autoinc_sst_mariabackup
- Closed