linux-traipu team mailing list archive

[Daniel Nichter <daniel@xxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/743958

Title:
  need way to determine master status/information from slave

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed

Bug description:
  If the slave can not connect to the master, currently error messages
  are printed out using errmsg_printf. There should be a status field or
  table in the sys_replication database that would show the error
  message trying to connect to the master, something to give a hint
  there is a problem. Currently if your not looking at drizzled in the
  console you have know way of knowing the master is inaccessible.

  A table should also exist, that shows the masters information,
  currently the only way to find that is look it up in slave.cfg file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/743958/+subscriptions