[MDEV-5072] status variable Slave_running show off in slave with more than one master Created: 2013-09-26 Updated: 2022-10-31 Resolved: 2022-10-31 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Documentation, Replication |
| Affects Version/s: | 10.0.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | aravinth (Inactive) | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
centos 6.4 |
||
| Description |
|
Configure a maria slave with 2 masters each replicating a different database. The status variable slave_running show "OFF" . Both sql and io thread status is fine in both the slave connections.
|
| Comments |
| Comment by Elena Stepanova [ 2013-10-06 ] |
|
The current logic is such that the Slave_running status variable indicates the status of the default slave (the one that default_status_connection variable is set to). The default value of default_status_connection is an empty line, which relates to the unnamed slave configured by the legacy syntax, when you just say I agree that the behavior is not obvious, and there were plans to sort out slave-related status and server variables. I'll assign it to Monty to decide what can be done about this one. |
| Comment by Sergei Golubchik [ 2022-10-31 ] |
|
Documentation now says that explicitly. |