You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some new backlog metrics that are useful. We could potentially tag by slave IP as well, although it might be tricky to resolve it to a specific host.
New metrics:
redis.replication.backlog_histlen shows the current replication backlog size in bytes used from the allocated repl-backlog-size in the config.
redis.replication.master_repl_offset
this metric is available on masters, it shows the current offset of the replication process on the master in bytes
redis.replication.slave_repl_offset idem for the slaves.
redis.replication.delay on masters only, measures the difference between the last offset reported by the slave and the current replication offset, which indicates how far your slave is behind. This metric is tagged by slave_ip, slave_port and slave_id (internal ID in the master).
Also added on Travis a replication config between the two instances we
have to assert the presence of this new metric.
Bonus: now the redis instances that were launched by the CI are cleaned
properly by the cleanup task.
see issue #915
There are some new backlog metrics that are useful. We could potentially tag by slave IP as well, although it might be tricky to resolve it to a specific host.
From a master:
From a slave:
The text was updated successfully, but these errors were encountered: