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
Add required heiradata to disable rdb_save_incremental_fsync
redis::rdb_save_incremental_fsync: false
What are you seeing
When rdb_save_incremental_fsync is set to false, redis should not use rdb-save-incremental-fsync. The CLI shows that it is still enabled:
$ redis-cli
127.0.0.1:6379> config get rdb-save-incremental-fsync
1) "rdb-save-incremental-fsync"
2) "yes"
The relevant config also does not appear in redis.conf:
# When redis saves RDB file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
<blank line where i would expect to see "rdb-save-incremental-fsync no">
What behaviour did you expect instead
the line:
rdb-save-incremental-fsync no
to appear in redis.conf when rdb-save-incremental-fsync is false or undef
the line
rdb-save-incremental-fsync yes
to appear in redis.conf when rdb-save-incremental-fsync is true
Output log
n/a
Any additional information you'd like to impart
I believe this to be happening due to the assumption that rdb-save-incremental-fsync is off by default. I have a PR to fix this that'll be along momentarily.
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
master
How to reproduce (e.g Puppet code you use)
redis
module:include redis
rdb_save_incremental_fsync
What are you seeing
When
rdb_save_incremental_fsync
is set tofalse
, redis should not userdb-save-incremental-fsync
. The CLI shows that it is still enabled:The relevant config also does not appear in
redis.conf
:What behaviour did you expect instead
the line:
to appear in
redis.conf
whenrdb-save-incremental-fsync
isfalse
orundef
the line
to appear in
redis.conf
whenrdb-save-incremental-fsync
istrue
Output log
n/a
Any additional information you'd like to impart
I believe this to be happening due to the assumption that
rdb-save-incremental-fsync
is off by default. I have a PR to fix this that'll be along momentarily.The text was updated successfully, but these errors were encountered: