Tim Landscheidt <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
                 CC|                            |
         Resolution|FIXED                       |---

--- Comment #4 from Tim Landscheidt <> ---
(In reply to comment #3)
> Looks like it's working fine to me.

No, as discussed on IRC, it's still running under my personal account.

As it would be useful to show replication lag for every MariaDB slave, I wanted
to discuss this as a wider change with Asher.  But:

a) chance never came about, and
b) it's already there!  For db1035, go to
and search for "mysql_slave_lag".

However, this isn't available for labsdb* yet (cf.,
and at the moment can't be enabled anyway as the monitoring for db1035 et al.
assumes that only /one/ MariaDB instance runs on any server, while on labsdb*
there are several and so mysql_slave_log & Co. need to be prefixed by, for
example, "s1_".

So to resolve this bug, we need to:

a) refactor the monitoring bits and pieces that they handle multiple instances
on one server,
b) enable such monitoring for labsdb*, and
c) create a ganglia::view where *_mysql_slave_lag for labsdb* is combined in
one report so that the information isn't scattered over three pages and
literally hundreds of graphs.

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to