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

rdb_save_incremental_fsync cannot be turned off #494

Open
thejambavan opened this issue Nov 9, 2023 · 0 comments · May be fixed by #495
Open

rdb_save_incremental_fsync cannot be turned off #494

thejambavan opened this issue Nov 9, 2023 · 0 comments · May be fixed by #495
Labels
bug Something isn't working

Comments

@thejambavan
Copy link

thejambavan commented Nov 9, 2023

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7.26.0
  • Ruby: ruby 2.7.8p225 (2023-03-30 revision 1f4d455848) [x86_64-linux]
  • Distribution: Ubuntu 22.04.3
  • Module version: 9.2.0 and master

How to reproduce (e.g Puppet code you use)

  1. Include the redis module:
include redis
  1. 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.

@thejambavan thejambavan linked a pull request Nov 9, 2023 that will close this issue
@kenyon kenyon added the bug Something isn't working label Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants