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
-
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | Galera [ 10124 ] | |
Component/s | Server [ 13907 ] |
Assignee | Jan Lindström [ jplindst ] |
Fix Version/s | 10.3 [ 22126 ] |
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 node restarted. |
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. |
Attachment | screenshot-1.png [ 46606 ] |
Fix Version/s | 10.4 [ 22408 ] |
Link |
This issue relates to |
Support case ID | 26355 | 26355 27240 |
Affects Version/s | 10.3.14 [ 23216 ] |
Affects Version/s | 10.3.11 [ 23141 ] |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Assignee | Jan Lindström [ jplindst ] | Daniele Sciascia [ sciascid ] |
Affects Version/s | 10.3.15 [ 23309 ] |
Assignee | Daniele Sciascia [ sciascid ] | Jan Lindström [ jplindst ] |
Assignee | Jan Lindström [ jplindst ] | Marko Mäkelä [ marko ] |
Status | Confirmed [ 10101 ] | In Review [ 10002 ] |
Priority | Major [ 3 ] | Critical [ 2 ] |
Assignee | Marko Mäkelä [ marko ] | Daniele Sciascia [ sciascid ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
issue.field.resolutiondate | 2019-05-21 12:09:42.0 | 2019-05-21 12:09:42.343 |
Fix Version/s | 10.3.16 [ 23410 ] | |
Fix Version/s | 10.4.6 [ 23412 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link |
This issue is caused by |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 90107 ] | MariaDB v4 [ 155060 ] |
Link |
This issue causes |
Zendesk Related Tickets | 196470 181484 171925 141968 135350 |