[MCOL-5052] Primary mismatch after restart : MXS vs MCS - Jira

Details

Type: Task
Status: Closed (View Workflow)
Priority: Major
Resolution: Not a Bug
Affects Version/s: None
Fix Version/s: cmapi-1.6.3
Component/s: cmapi
Labels:
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

alexey vorovich (Inactive) added a comment - 2022-04-13 20:19

More on the subject . It turns out that after some wait (1-2 min) the MCS switches the primary to match MXS.

Unless there are objections , I will cancel the Jira tomorrow

alexey vorovich (Inactive) added a comment - 2022-04-13 20:19 More on the subject . It turns out that after some wait (1-2 min) the MCS switches the primary to match MXS. Unless there are objections , I will cancel the Jira tomorrow

People

Assignee:: Alan Mologorsky

Reporter:: alexey vorovich (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2022-04-13 16:05

Updated:: 2022-04-14 20:40

Resolved:: 2022-04-14 20:39

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB ColumnStore