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
We are running KeyDB as a replacement to one of our production Redis Cluster shards. Basically we took the same config file, added some KeyDB-related settings (server-threads, etc) and basically switched all the nodes within one cluster shard to KeyDB.
The reported behavior occurred only on the primary (master) node, did not occur on secondaries (slaves).
The rest of the cluster remained on Redis 5.x.
After downgrading to 6.2 the problem stopped occurring and everything runs smooth and stable.
Probably, exactly 27cb5db for v. 6.3.2 might have caused the problem.
Oh, and please don't be confused with /usr/local/bin/redis-server binary path - it's KeyDB, we just had to rename the binary as our monitoring currently uses Prometheus Named Process Group exporter which monitors redis-server, and, since it is a test-drive, we have just kept the process name.
Crash report
Paste the complete crash log between the quotes below. Please include a few lines from the log preceding the crash report to provide some context.
Aditional information
Ubuntu 18.04.4, Linux 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux.
The server has crashed and gracefully restarted.
Probably somehow related to problem depicted in #250
The text was updated successfully, but these errors were encountered: