Open rnz opened 2 years ago
Hi @rnz I could not reproduce this bug. Based on this error message you provided "Could not connect to Redis at /proc/20715: Operation not permitted", I believe it may be a permission issue, have you tried running "sudo redis-cli -s /proc/$(pgrep keydb-server)/root/tmp/keydb.sock info | grep ops"?
@MalavanEQAlpha may be load is not havy?
@rnz have you tried looking at permissions per Malavan's suggestion under your specific load?
@MalavanEQAlpha, @benschermel i think that is not permission issue. That message "Could not connect to Redis at /proc/20715: Operation not permitted" appears beetwen loops the command INFO return result.
Describe the bug
To reproduce
enable unixsocket start keydb-server after start add workload - 90k ops run in one terminal session:
$ watch -n0 "keydb-cli -s /proc/$(pgrep keydb-server)/root/tmp/keydb.sock info | grep ops"
look at log in other terminal session:$ tail -f /var/log/keydb/keydb-server.log
Expected behavior
unixsocket is accesible when background save
Additional information
host info about zfs dataset: