New in INFO: aof_last_bgrewrite_status #586

merged 1 commit into from Jul 27, 2012


None yet

2 participants


AOF rewriting is too important to go unmonitored. Redis can easily fill its filesystem with AOF data if failing rewrites go unnoticed by operators. This pull request introduces a new data point in INFO that behaves just like rdb_last_bgsave_status for AOF persistence.

@saj saj New in INFO: aof_last_bgrewrite_status
Behaves like rdb_last_bgsave_status -- even down to reporting 'ok' when
no rewrite has been done yet.  (You might want to check that
aof_last_rewrite_time_sec is not -1.)
@antirez antirez merged commit 04950a9 into antirez:unstable Jul 27, 2012

Thanks! merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment