[MXS-1251] detect_replication_lag can break replication failover - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Not a Bug
Affects Version/s: 2.0.5
Fix Version/s: N/A
Component/s: mariadbmon
Labels:
None

Sprint:
2017-42

Description

when maxscale is setup to monitor replication lag . Maxscale can run SQL command on the slaves

CREATE DATABASE IF NOT EXISTS maxscale_schema;

CREATE TABLE IF NOT EXISTS maxscale_schema.replication_heartbeat (maxscale_id INT NOT NULL, master_server_id INT NOT NULL, master_timestamp INT UNSIGNED NOT NULL, PRIMARY KEY ( master_server_id, maxscale_id ) ) ENGINE=MYISAM DEFAULT CHARSET=latin1;

CREATE DATABASE IF NOT EXISTS maxscale_schema;

CREATE TABLE IF NOT EXISTS maxscale_schema.replication_heartbeat (maxscale_id INT NOT NULL, master_server_id INT NOT NULL, master_timestamp INT UNSIGNED NOT NULL, PRIMARY KEY ( master_server_id, maxscale_id ) ) ENGINE=MYISAM DEFAULT CHARSET=latin1;

I propose that when state is slave and no table is discovered such insert are made on the master , and until it discovered monitor replication delay is disable

Attachments

Activity

People

Assignee:: markus makela

Reporter:: VAROQUI Stephane

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2017-04-25 12:53

Updated:: 2017-09-20 08:04

Resolved:: 2017-09-20 08:04

Git Integration

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