Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
None
-
None
Description
After the primary (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation
and in
https://jira.mariadb.org/browse/MCOL-4939
The problem goes back to mariadb/skysql-enterprise-columnstore:sky-5.5.2-1-GA
from last June
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | After the primary pod (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary . |
After the primary pod (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation and in https://jira.mariadb.org/browse/MCOL-4939 |
| Description |
After the primary pod (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation and in https://jira.mariadb.org/browse/MCOL-4939 |
After the primary pod (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation and in https://jira.mariadb.org/browse/MCOL-4939 The problem goes back to mariadb/skysql-enterprise-columnstore:sky-5.5.2-1-GA from last June |
| Assignee | Alan Mologorsky [ JIRAUSER49150 ] |
| Summary | Primary mismatch after pod restart : MXS vs MCS | Primary mismatch after restart : MXS vs MCS |
| Description |
After the primary pod (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation and in https://jira.mariadb.org/browse/MCOL-4939 The problem goes back to mariadb/skysql-enterprise-columnstore:sky-5.5.2-1-GA from last June |
After the primary (node 1) in a cluster is killed and then restarted , we have a discrepancy between MXS showing node 2 as primary and MCS showing node 1 as primary .
The details are in https://mariadbcorp.atlassian.net/wiki/spaces/~695761903/pages/1629783457/CMAPI+primary+mismatch+observation and in https://jira.mariadb.org/browse/MCOL-4939 The problem goes back to mariadb/skysql-enterprise-columnstore:sky-5.5.2-1-GA from last June |
| Fix Version/s | cmapi-1.6.3 [ 27900 ] |
| Resolution | Not a Bug [ 6 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |