Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis: fetch additional replication metrics available in 2.8 #915

Closed
conorbranagan opened this issue Apr 24, 2014 · 2 comments
Closed

Redis: fetch additional replication metrics available in 2.8 #915

conorbranagan opened this issue Apr 24, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@conorbranagan
Copy link
Contributor

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:

# Replication
role:master
connected_slaves:1
slave0:ip=*.*.*.*,port=6379,state=online,offset=19697,lag=0
master_repl_offset:19697
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:2
repl_backlog_histlen:19696

From a slave:

# Replication
role:slave
master_host:*.*.*.*
master_port:6379
master_link_status:up
master_last_io_seconds_ago:4
master_sync_in_progress:0
slave_repl_offset:19837
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0
@remh
Copy link

remh commented May 19, 2014

Moving that for 5.x

@remh remh added this to the 5.0 milestone May 19, 2014
@remh remh modified the milestones: 5.1.0, 5.0 Jun 10, 2014
@remh remh modified the milestones: 5.2.0, 5.1.0 Sep 26, 2014
@remh remh modified the milestones: 5.3.0, 5.2.0 Jan 13, 2015
@remh remh assigned hkaj Feb 3, 2015
hkaj added a commit that referenced this issue Feb 23, 2015
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
@remh
Copy link

remh commented Feb 27, 2015

Fixed by #1350

@remh remh closed this as completed Feb 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants