Is there a way to specify the mode (gtid, pseudo, smart) for a graceful-master-takeover from the api or cli?
128 views
Skip to first unread message
Laurent Indermühle
Nov 27, 2019, 5:18:23 AM11/27/19
to orchestrator-mysql
Hello Orchestrator group,
I'm using GTID for MySQL 5.7 and MariaDB 10.4. The following question is the same for both versions.
Doing a graceful-master-takeover from the GUI works because you can change the drop down menu and specify "Gtid Mode".
As a side note, the Smart Mode doesn't seem to be that smart:
In "Smart Mode", after a graceful-master-takeover done into the GUI, the new slave doesn't use Gtid anymore.
My question is: How to specify the mode from the API or the CLI? I need this, because I use a script to run the graceful-master-takeover so the GUI is not helpful.
Did I miss something?
Best regards,
Laurent
Laurent Indermühle
Nov 27, 2019, 5:22:48 AM11/27/19
to orchestrator-mysql
Also, I noticed in the Recovery log of the GUI this:
All errors:
PseudoGTIDPattern not configured; cannot use Pseudo-GTIDMaybe this is related.
Shlomi Noach
Nov 27, 2019, 6:12:18 AM11/27/19
to Laurent Indermühle, orchestrator-mysql
I have no answer for MariaDB (no personal experience).
Can you please confirm with your GTID setup, do you have `AUTO_POSITION: 1` in `SHOW SLAVE STATUS`? Otherwise this isn't a true GTID replication.
If you're using GTID, graceful-master-takeover should work (it does for us) and orchestrator shouldn't say anything about PseudoGTID. The fast that it _does_ say aomething about PseudoGTID suggests your replication setup doesn't use GTID.
Anyway that's my immediate guess.
--
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-my...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/b932df51-346e-4304-ade3-a583c0b556c3%40googlegroups.com.
Laurent Indermühle
Nov 27, 2019, 6:52:53 AM11/27/19
to orchestrator-mysql
Hello Shlomi,
Thanks for your answer!
Yes, I had `AUTO_POSITION: 1`.
Here's how I have started the replication:
MySQL:
CHANGE MASTER TO
master_host='<master>.example.com',
master_port=<port>,
master_user='replication',
master_password='<password>',
master_connect_retry = 1,
master_auto_position=1;And the my.cnf for MySQL:binlog_format = MIXED
log_slave_updates = ON
enforce_gtid_consistency = ON
gtid_mode = ON
MariaDB:
CHANGE MASTER TO
master_host='<master>.example.com',
master_port=<port>,
master_user='replication',
master_password='<password>',
master_connect_retry = 1,
master_use_gtid=current_pos;
And the my.cnf for MariaDB:gtid_strict_mode = ON
binlog_format = MIXED
log_slave_updates = ON
I'm starting to search why Orchestrator complain about PseudoGTID. Thanks for the lead.On Wednesday, November 27, 2019 at 12:12:18 PM UTC+1, Shlomi Noach wrote:
I have no answer for MariaDB (no personal experience).Can you please confirm with your GTID setup, do you have `AUTO_POSITION: 1` in `SHOW SLAVE STATUS`? Otherwise this isn't a true GTID replication.If you're using GTID, graceful-master-takeover should work (it does for us) and orchestrator shouldn't say anything about PseudoGTID. The fast that it _does_ say aomething about PseudoGTID suggests your replication setup doesn't use GTID.Anyway that's my immediate guess.
On Wed, Nov 27, 2019 at 12:18 PM Laurent Indermühle <laurent.i...@gmail.com> wrote:
--Hello Orchestrator group,I'm using GTID for MySQL 5.7 and MariaDB 10.4. The following question is the same for both versions.Doing a graceful-master-takeover from the GUI works because you can change the drop down menu and specify "Gtid Mode".As a side note, the Smart Mode doesn't seem to be that smart:In "Smart Mode", after a graceful-master-takeover done into the GUI, the new slave doesn't use Gtid anymore.My question is: How to specify the mode from the API or the CLI? I need this, because I use a script to run the graceful-master-takeover so the GUI is not helpful.Did I miss something?Best regards,Laurent
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-mysql+unsub...@googlegroups.com.
Laurent Indermühle
Nov 27, 2019, 9:27:39 AM11/27/19
to orchestrator-mysql
I've found something weird.
I was doing the graceful-master-takeover with a maintenance like so:
api "begin-maintenance/${master}/${orc-hostname}/${reason}"
api "graceful-master-takeover/${master}"
print_response | filter_graceful_returned_message
api "end-maintenance/${master}"I tried to remove the maintenance part, and now the GTID is kept for MySQL (MariaDB still doesn't work).
Is it possible that the maintenance change the behavior of the graceful-master-takeover?
Shlomi Noach
Nov 27, 2019, 9:30:01 AM11/27/19
to Laurent Indermühle, orchestrator-mysql
Laurent, maintenance is something that orchestrator should manage internally; I can understand how this causes confusion; but orchestrator uses maintenance to keep its own operations isolated from each other, and from other people operating on nodes in maintenance. I'd suggest not using begin/end-maintenance.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-my...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/b932df51-346e-4304-ade3-a583c0b556c3%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-my...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/b9aa1086-bfb1-4898-baa5-c651c01842d1%40googlegroups.com.
Shlomi Noach
Nov 27, 2019, 10:18:08 AM11/27/19
to Laurent Indermühle, orchestrator-mysql
I'd be curious to see output of `select * from database_instance where ... \G` (pick your specific hosts or cluster; e.g. `hostname=?` or `suggested_cluster_alias=?`)
This will tell us what orchestrator things about GTID replication for those servers.
Shlomi Noach
Nov 27, 2019, 10:18:46 AM11/27/19
to Laurent Indermühle, orchestrator-mysql
uhhh... also good to `orchestrator-client -c api -path instance/<hostname>/3306` | jq .
to get a JSON dump
Laurent Indermühle
Nov 27, 2019, 10:38:17 AM11/27/19
to orchestrator-mysql
Here is the query with all my slaves:
*************************** 1. row ***************************
hostname: mdb-scx-dbm-01-m-d.example.com
port: 33001
last_checked: 2019-11-27 16:29:45
last_attempted_check: 2019-11-27 16:29:45
last_check_partial_success: 1
last_seen: 2019-11-27 16:29:45
uptime: 806874
server_id: 1
server_uuid: 3a4e8c97-e50c-11e9-903c-0050568423fe
version: 5.7.26-log
binlog_server: 0
read_only: 1
binlog_format: MIXED
log_bin: 1
log_slave_updates: 1
binary_log_file: mysqld1-bin.000065
binary_log_pos: 234
master_host: mdb-scx-dbs-01-i-d.example.com
master_port: 33001
slave_sql_running: 1
slave_io_running: 1
replication_sql_thread_state: 1
replication_io_thread_state: 1
has_replication_filters: 0
oracle_gtid: 1
master_uuid: 152043da-ffe1-11e9-84dc-0050568470dc
ancestry_uuid: 152043da-ffe1-11e9-84dc-0050568470dc,3a4e8c97-e50c-11e9-903c-0050568423fe
executed_gtid_set: 152043da-ffe1-11e9-84dc-0050568470dc:1-3,
3a4e8c97-e50c-11e9-903c-0050568423fe:1-47126
gtid_purged: 152043da-ffe1-11e9-84dc-0050568470dc:1,
3a4e8c97-e50c-11e9-903c-0050568423fe:1-47126
gtid_errant:
supports_oracle_gtid: 1
mariadb_gtid: 0
pseudo_gtid: 0
master_log_file: mysqld1-bin.000026
read_master_log_pos: 234
relay_master_log_file: mysqld1-bin.000026
exec_master_log_pos: 234
relay_log_file: mdb-scx-dbm-01-m-d-relay-bin.000002
relay_log_pos: 371
last_sql_error:
last_io_error:
seconds_behind_master: 0
slave_lag_seconds: 0
sql_delay: 0
allow_tls: 0
num_slave_hosts: 0
slave_hosts: []
cluster_name: mdb-scx-dbs-01-i-d.example.com:33001
suggested_cluster_alias: mdb-scx-dev:mysqld1
data_center: MA
region:
physical_environment:
instance_alias: mysqld1
semi_sync_enforced: 0
replication_depth: 1
is_co_master: 0
replication_credentials_available: 1
has_replication_credentials: 1
version_comment: MySQL Community Server (GPL)
major_version: 5.7
binlog_row_image: FULL
last_discovery_latency: 6066388
semi_sync_master_enabled: 0
semi_sync_replica_enabled: 0
gtid_mode: ON
*************************** 2. row ***************************
hostname: mdb-scx-dbm-01-m-d.example.com
port: 33002
last_checked: 2019-11-27 16:29:49
last_attempted_check: 2019-11-27 16:29:49
last_check_partial_success: 1
last_seen: 2019-11-27 16:29:49
uptime: 806877
server_id: 2
server_uuid: 4d0d98a9-00b1-11ea-90e2-0050568423fe
version: 5.7.28-log
binlog_server: 0
read_only: 1
binlog_format: MIXED
log_bin: 1
log_slave_updates: 1
binary_log_file: mysqld2-bin.000006
binary_log_pos: 637
master_host: mdb-scx-dbs-01-i-d.example.com
master_port: 33002
slave_sql_running: 1
slave_io_running: 1
replication_sql_thread_state: 1
replication_io_thread_state: 1
has_replication_filters: 0
oracle_gtid: 1
master_uuid: 01897385-00b3-11ea-9959-0050568470dc
ancestry_uuid: 01897385-00b3-11ea-9959-0050568470dc,4d0d98a9-00b1-11ea-90e2-0050568423fe
executed_gtid_set: 01897385-00b3-11ea-9959-0050568470dc:1-3,
4d0d98a9-00b1-11ea-90e2-0050568423fe:1-36
gtid_purged: 4d0d98a9-00b1-11ea-90e2-0050568423fe:1-8
gtid_errant:
supports_oracle_gtid: 1
mariadb_gtid: 0
pseudo_gtid: 0
master_log_file: mysqld2-bin.000004
read_master_log_pos: 637
relay_master_log_file: mysqld2-bin.000004
exec_master_log_pos: 637
relay_log_file: mdb-scx-dbm-01-m-d-relay-bin.000002
relay_log_pos: 420
last_sql_error:
last_io_error:
seconds_behind_master: 0
slave_lag_seconds: 0
sql_delay: 0
allow_tls: 0
num_slave_hosts: 0
slave_hosts: []
cluster_name: mdb-scx-dbs-01-i-d.example.com:33002
suggested_cluster_alias: mdb-scx-dev:mysqld2
data_center: MA
region:
physical_environment:
instance_alias: mysqld2
semi_sync_enforced: 0
replication_depth: 1
is_co_master: 0
replication_credentials_available: 1
has_replication_credentials: 1
version_comment: MySQL Community Server (GPL)
major_version: 5.7
binlog_row_image: FULL
last_discovery_latency: 16413037
semi_sync_master_enabled: 0
semi_sync_replica_enabled: 0
gtid_mode: ON
*************************** 3. row ***************************
hostname: mdb-scx-dbm-01-m-d.example.com
port: 33003
last_checked: 2019-11-27 16:29:49
last_attempted_check: 2019-11-27 16:29:49
last_check_partial_success: 1
last_seen: 2019-11-27 16:29:49
uptime: 806876
server_id: 3
server_uuid: a1061dad-0167-11ea-ae71-0050568423fe
version: 5.7.21-log
binlog_server: 0
read_only: 1
binlog_format: MIXED
log_bin: 1
log_slave_updates: 1
binary_log_file: mysqld3-bin.000006
binary_log_pos: 637
master_host: mdb-scx-dbs-01-i-d.example.com
master_port: 33003
slave_sql_running: 1
slave_io_running: 1
replication_sql_thread_state: 1
replication_io_thread_state: 1
has_replication_filters: 0
oracle_gtid: 1
master_uuid: 6e69936e-0168-11ea-8655-0050568470dc
ancestry_uuid: 6e69936e-0168-11ea-8655-0050568470dc,a1061dad-0167-11ea-ae71-0050568423fe
executed_gtid_set: 6e69936e-0168-11ea-8655-0050568470dc:1-3,
a1061dad-0167-11ea-ae71-0050568423fe:1-27
gtid_purged: a1061dad-0167-11ea-ae71-0050568423fe:1-8
gtid_errant:
supports_oracle_gtid: 1
mariadb_gtid: 0
pseudo_gtid: 0
master_log_file: mysqld3-bin.000004
read_master_log_pos: 637
relay_master_log_file: mysqld3-bin.000004
exec_master_log_pos: 637
relay_log_file: mdb-scx-dbm-01-m-d-relay-bin.000002
relay_log_pos: 420
last_sql_error:
last_io_error:
seconds_behind_master: 0
slave_lag_seconds: 0
sql_delay: 0
allow_tls: 0
num_slave_hosts: 0
slave_hosts: []
cluster_name: mdb-scx-dbs-01-i-d.example.com:33003
suggested_cluster_alias: mdb-scx-dev:mysqld3
data_center: MA
region:
physical_environment:
instance_alias: mysqld3
semi_sync_enforced: 0
replication_depth: 1
is_co_master: 0
replication_credentials_available: 1
has_replication_credentials: 1
version_comment: MySQL Community Server (GPL)
major_version: 5.7
binlog_row_image: FULL
last_discovery_latency: 10926182
semi_sync_master_enabled: 0
semi_sync_replica_enabled: 0
gtid_mode: ON
*************************** 4. row ***************************
hostname: mdb-scx-dbm-01-m-d.example.com
port: 33004
last_checked: 2019-11-27 16:29:49
last_attempted_check: 2019-11-27 16:29:49
last_check_partial_success: 1
last_seen: 2019-11-27 16:29:49
uptime: 9639
server_id: 4
server_uuid:
version: 10.4.6-MariaDB-log
binlog_server: 0
read_only: 1
binlog_format: MIXED
log_bin: 1
log_slave_updates: 1
binary_log_file: mysqld4-bin.000003
binary_log_pos: 2383
master_host: mdb-scx-dbs-01-i-d.example.com
master_port: 33004
slave_sql_running: 1
slave_io_running: 1
replication_sql_thread_state: 1
replication_io_thread_state: 1
has_replication_filters: 0
oracle_gtid: 0
master_uuid: No
ancestry_uuid:
executed_gtid_set:
gtid_purged:
gtid_errant:
supports_oracle_gtid: 0
mariadb_gtid: 0
pseudo_gtid: 0
master_log_file: mysqld4-bin.000001
read_master_log_pos: 7113
relay_master_log_file: mysqld4-bin.000001
exec_master_log_pos: 7113
relay_log_file: mysqld4-relay-bin.000002
relay_log_pos: 557
last_sql_error:
last_io_error:
seconds_behind_master: 0
slave_lag_seconds: 0
sql_delay: 0
allow_tls: 0
num_slave_hosts: 0
slave_hosts: []
cluster_name: mdb-scx-dbs-01-i-d.example.com:33004
suggested_cluster_alias: mdb-scx-dev:mysqld4
data_center: MA
region:
physical_environment:
instance_alias: mysqld4
semi_sync_enforced: 0
replication_depth: 1
is_co_master: 0
replication_credentials_available: 0
has_replication_credentials: 1
version_comment: MariaDB Server
major_version: 10.4
binlog_row_image:
last_discovery_latency: 19908572
semi_sync_master_enabled: 0
semi_sync_replica_enabled: 0
gtid_mode:
*************************** 5. row ***************************
hostname: mdb-scx-dbm-01-m-d.example.com
port: 33005
last_checked: 2019-11-27 16:29:49
last_attempted_check: 2019-11-27 16:29:49
last_check_partial_success: 1
last_seen: 2019-11-27 16:29:49
uptime: 6973
server_id: 5
server_uuid:
version: 10.4.10-MariaDB-log
binlog_server: 0
read_only: 1
binlog_format: MIXED
log_bin: 1
log_slave_updates: 1
binary_log_file: mysqld5-bin.000002
binary_log_pos: 389
master_host: mdb-scx-dbs-01-i-d.example.com
master_port: 33005
slave_sql_running: 1
slave_io_running: 1
replication_sql_thread_state: 1
replication_io_thread_state: 1
has_replication_filters: 0
oracle_gtid: 0
master_uuid: No
ancestry_uuid:
executed_gtid_set:
gtid_purged:
gtid_errant:
supports_oracle_gtid: 0
mariadb_gtid: 0
pseudo_gtid: 0
master_log_file: mysqld5-bin.000001
read_master_log_pos: 5496
relay_master_log_file: mysqld5-bin.000001
exec_master_log_pos: 5496
relay_log_file: mysqld5-relay-bin.000002
relay_log_pos: 557
last_sql_error:
last_io_error:
seconds_behind_master: 0
slave_lag_seconds: 0
sql_delay: 0
allow_tls: 0
num_slave_hosts: 0
slave_hosts: []
cluster_name: mdb-scx-dbs-01-i-d.example.com:33005
suggested_cluster_alias: mdb-scx-dev:mysqld5
data_center: MA
region:
physical_environment:
instance_alias: mysqld5
semi_sync_enforced: 0
replication_depth: 1
is_co_master: 0
replication_credentials_available: 0
has_replication_credentials: 1
version_comment: MariaDB Server
major_version: 10.4
binlog_row_image:
last_discovery_latency: 17812209
semi_sync_master_enabled: 0
semi_sync_replica_enabled: 0
gtid_mode:
this is a api returned value for a MySQL Slave :
{
"Key": {
"Hostname": "mdb-scx-dbm-01-m-d.example.com",
"Port": 33001
},
"InstanceAlias": "mysqld1",
"Uptime": 807090,
"ServerID": 1,
"ServerUUID": "3a4e8c97-e50c-11e9-903c-0050568423fe",
"Version": "5.7.26-log",
"VersionComment": "MySQL Community Server (GPL)",
"FlavorName": "MySQL",
"ReadOnly": true,
"Binlog_format": "MIXED",
"BinlogRowImage": "FULL",
"LogBinEnabled": true,
"LogSlaveUpdatesEnabled": true,
"SelfBinlogCoordinates": {
"LogFile": "mysqld1-bin.000065",
"LogPos": 234,
"Type": 0
},
"MasterKey": {
"Hostname": "mdb-scx-dbs-01-i-d.example.com",
"Port": 33001
},
"MasterUUID": "152043da-ffe1-11e9-84dc-0050568470dc",
"AncestryUUID": "152043da-ffe1-11e9-84dc-0050568470dc,3a4e8c97-e50c-11e9-903c-0050568423fe",
"IsDetachedMaster": false,
"Slave_SQL_Running": true,
"Slave_IO_Running": true,
"ReplicationSQLThreadState": 1,
"ReplicationIOThreadState": 1,
"HasReplicationFilters": false,
"GTIDMode": "ON",
"SupportsOracleGTID": true,
"UsingOracleGTID": true,
"UsingMariaDBGTID": false,
"UsingPseudoGTID": false,
"ReadBinlogCoordinates": {
"LogFile": "mysqld1-bin.000026",
"LogPos": 234,
"Type": 0
},
"ExecBinlogCoordinates": {
"LogFile": "mysqld1-bin.000026",
"LogPos": 234,
"Type": 0
},
"IsDetached": false,
"RelaylogCoordinates": {
"LogFile": "mdb-scx-dbm-01-m-d-relay-bin.000002",
"LogPos": 371,
"Type": 1
},
"LastSQLError": "",
"LastIOError": "",
"SecondsBehindMaster": {
"Int64": 0,
"Valid": true
},
"SQLDelay": 0,
"ExecutedGtidSet": "152043da-ffe1-11e9-84dc-0050568470dc:1-3,\n3a4e8c97-e50c-11e9-903c-0050568423fe:1-47126",
"GtidPurged": "152043da-ffe1-11e9-84dc-0050568470dc:1,\n3a4e8c97-e50c-11e9-903c-0050568423fe:1-47126",
"GtidErrant": "",
"SlaveLagSeconds": {
"Int64": 0,
"Valid": true
},
"SlaveHosts": [],
"ClusterName": "mdb-scx-dbs-01-i-d.example.com:33001",
"SuggestedClusterAlias": "mdb-scx-dev:mysqld1",
"DataCenter": "MA",
"Region": "",
"PhysicalEnvironment": "",
"ReplicationDepth": 1,
"IsCoMaster": false,
"HasReplicationCredentials": true,
"ReplicationCredentialsAvailable": true,
"SemiSyncEnforced": false,
"SemiSyncMasterEnabled": false,
"SemiSyncReplicaEnabled": false,
"LastSeenTimestamp": "2019-11-27 16:33:21",
"IsLastCheckValid": true,
"IsUpToDate": false,
"IsRecentlyChecked": true,
"SecondsSinceLastSeen": {
"Int64": 6,
"Valid": true
},
"CountMySQLSnapshots": 0,
"IsCandidate": false,
"PromotionRule": "neutral",
"IsDowntimed": false,
"DowntimeReason": "",
"DowntimeOwner": "",
"DowntimeEndTimestamp": "",
"ElapsedDowntime": 0,
"UnresolvedHostname": "",
"AllowTLS": false,
"Problems": [],
"LastDiscoveryLatency": 5761147
}
Here is a api returned value for a MariaDB slave:
{
"Key": {
"Hostname": "mdb-scx-dbm-01-m-d.example.com",
"Port": 33005
},
"InstanceAlias": "mysqld5",
"Uptime": 7333,
"ServerID": 5,
"ServerUUID": "",
"Version": "10.4.10-MariaDB-log",
"VersionComment": "MariaDB Server",
"FlavorName": "MariaDB",
"ReadOnly": true,
"Binlog_format": "MIXED",
"BinlogRowImage": "",
"LogBinEnabled": true,
"LogSlaveUpdatesEnabled": true,
"SelfBinlogCoordinates": {
"LogFile": "mysqld5-bin.000002",
"LogPos": 389,
"Type": 0
},
"MasterKey": {
"Hostname": "mdb-scx-dbs-01-i-d.example.com",
"Port": 33005
},
"MasterUUID": "No",
"AncestryUUID": "",
"IsDetachedMaster": false,
"Slave_SQL_Running": true,
"Slave_IO_Running": true,
"ReplicationSQLThreadState": 1,
"ReplicationIOThreadState": 1,
"HasReplicationFilters": false,
"GTIDMode": "",
"SupportsOracleGTID": false,
"UsingOracleGTID": false,
"UsingMariaDBGTID": false,
"UsingPseudoGTID": false,
"ReadBinlogCoordinates": {
"LogFile": "mysqld5-bin.000001",
"LogPos": 5496,
"Type": 0
},
"ExecBinlogCoordinates": {
"LogFile": "mysqld5-bin.000001",
"LogPos": 5496,
"Type": 0
},
"IsDetached": false,
"RelaylogCoordinates": {
"LogFile": "mysqld5-relay-bin.000002",
"LogPos": 557,
"Type": 1
},
"LastSQLError": "",
"LastIOError": "",
"SecondsBehindMaster": {
"Int64": 0,
"Valid": true
},
"SQLDelay": 0,
"ExecutedGtidSet": "",
"GtidPurged": "",
"GtidErrant": "",
"SlaveLagSeconds": {
"Int64": 0,
"Valid": true
},
"SlaveHosts": [],
"ClusterName": "mdb-scx-dbs-01-i-d.example.com:33005",
"SuggestedClusterAlias": "mdb-scx-dev:mysqld5",
"DataCenter": "MA",
"Region": "",
"PhysicalEnvironment": "",
"ReplicationDepth": 1,
"IsCoMaster": false,
"HasReplicationCredentials": true,
"ReplicationCredentialsAvailable": false,
"SemiSyncEnforced": false,
"SemiSyncMasterEnabled": false,
"SemiSyncReplicaEnabled": false,
"LastSeenTimestamp": "2019-11-27 16:35:49",
"IsLastCheckValid": true,
"IsUpToDate": true,
"IsRecentlyChecked": true,
"SecondsSinceLastSeen": {
"Int64": 5,
"Valid": true
},
"CountMySQLSnapshots": 0,
"IsCandidate": false,
"PromotionRule": "neutral",
"IsDowntimed": false,
"DowntimeReason": "",
"DowntimeOwner": "",
"DowntimeEndTimestamp": "",
"ElapsedDowntime": 0,
"UnresolvedHostname": "",
"AllowTLS": false,
"Problems": [],
"LastDiscoveryLatency": 16083096
}
I've also found that my orchestrator.conf.json is outdated. Many option have ben added since I saved it. But I've updated Orchestrator to the last version.
uhhh... also good to `orchestrator-client -c api -path instance/<hostname>/3306` | jq .to get a JSON dump
On Wed, Nov 27, 2019 at 5:17 PM Shlomi Noach <shlom...@gmail.com> wrote:
I'd be curious to see output of `select * from database_instance where ... \G` (pick your specific hosts or cluster; e.g. `hostname=?` or `suggested_cluster_alias=?`)This will tell us what orchestrator things about GTID replication for those servers.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-mysql+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orchestrator-mysql/b932df51-346e-4304-ade3-a583c0b556c3%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "orchestrator-mysql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orchestrator-mysql+unsub...@googlegroups.com.
Laurent Indermühle
Nov 29, 2019, 8:10:55 AM11/29/19
to orchestrator-mysql
What I don't get, is why Orchestrator think the master doesn't use GTID for MariaDB. It's built-in, you can't run without it.
Here is the output for MariaDB 10.4.10:
orchestrator -c topology -i mdb-scx-dbs-01-i-d.example.com:33005
mdb-scx-dbm-01-m-d.example.com:33005 [0s,ok,10.4.10-MariaDB-log,rw,MIXED,>>]
+ mdb-scx-dbs-01-i-d.example.com:33005 [0s,ok,10.4.10-MariaDB-log,ro,MIXED,>>,GTID]Should I open an issue?
I'm unable to find in the code where Orchestrator look for GTID support.
All I found is line 512 of instance_dao.go :
instance.UsingMariaDBGTID = (m.GetStringD("Using_Gtid", "No") != "No")This "Using_Gtid" is not available on the Master.
Danny
Jan 14, 2021, 8:33:00 AM1/14/21
to orchestrator-mysql
Did you ever get this resolved? I'm just starting down the Orchestrator path with MariaDB and seeing similar issues.
Thank you.
Laurent Indermühle
Jan 14, 2021, 4:06:02 PM1/14/21
to orchestrator-mysql
Hi Danny,
Sorry no. I've updated Orchestrator few times since but the issue is still there.
I am working on something else but I still plane to automate switchovers someday.
It's sad, because Orchestrator is fantastic. It sends me emails before our monitoring tool when there is issues with replication. And it's even its purpose!
Reply all
Reply to author
Forward
0 new messages