I reconfirm this bug:
$ cat slave/log Replication slave: Access denied for user 'foo' (using password: YES)
Ok so slave is _not_ connected to master, yet:
drizzle> select * from io_state\G *************************** 1. row *************************** master_id: 1 status: RUNNING error_msg:
drizzle> select * from applier_state\G *************************** 1. row *************************** master_id: 1 last_applied_commit_id: 5 originating_server_uuid: AB6FC4C5-C76A-4E7B-8488-5264F1F40424 originating_commit_id: 5 status: RUNNING error_msg:
Everything is RUNNING, which is wrong. These need to be STOPPED and there needs to be an error_msg.
I reconfirm this bug:
$ cat slave/log
Replication slave: Access denied for user 'foo' (using password: YES)
Ok so slave is _not_ connected to master, yet:
drizzle> select * from io_state\G ******* ******* ****** 1. row ******* ******* ******* ******
*******
master_id: 1
status: RUNNING
error_msg:
drizzle> select * from applier_state\G ******* ******* ****** 1. row ******* ******* ******* ******
master_ id: 1 commit_ id: 5 server_ uuid: AB6FC4C5- C76A-4E7B- 8488-5264F1F404 24 commit_ id: 5
status: RUNNING
error_msg:
*******
last_applied_
originating_
originating_
Everything is RUNNING, which is wrong. These need to be STOPPED and there needs to be an error_msg.