summaryrefslogtreecommitdiff
path: root/src/aof.c
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2012-03-25 11:27:35 +0200
committerantirez <antirez@gmail.com>2012-03-25 11:27:35 +0200
commitc1d01b3c5796ee7e3f466e0db9f55d37e843cbb9 (patch)
tree1bbdbb588580a46e8f74a04c2f2e055b479bae65 /src/aof.c
parent512f682340eb74aaedc525e834a943427999508c (diff)
downloadredis-c1d01b3c5796ee7e3f466e0db9f55d37e843cbb9.tar.gz
New INFO field aof_delayed_fsync introduced.
This new field counts all the times Redis is configured with AOF enabled and fsync policy 'everysec', but the previous fsync performed by the background thread was not able to complete within two seconds, forcing Redis to perform a write against the AOF file while the fsync is still in progress (likely a blocking operation).
Diffstat (limited to 'src/aof.c')
-rw-r--r--src/aof.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/aof.c b/src/aof.c
index 83633217f..4d3ce096a 100644
--- a/src/aof.c
+++ b/src/aof.c
@@ -108,6 +108,7 @@ void flushAppendOnlyFile(int force) {
}
/* Otherwise fall trough, and go write since we can't wait
* over two seconds. */
+ server.aof_delayed_fsync++;
redisLog(REDIS_NOTICE,"Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.");
}
}