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
[QUESTION] Redis crashes with the following error on multiple nodes. What could be the reason? #11314
Comments
After these errors the number of keys in Redis becomes '0' and it then recovers from either the persistence files or its corresponding master nodes |
@mukundv18 a few questions:
|
|
yes, you see the crash report in the redis log file. |
@oranagra
|
I see the following logs in the syslog from the time the keys became '0' until it recovered. It appears the data is loading in the slave nodes during that time. Any clues from these logs?
|
i'm out of ideas. |
These are the logs from redis.log file with some prior log statements and post log statements. Do these give any clue?
|
redis does normally accept client connections during this times. |
Do you need to see any specific config parameters to confirm the same? |
I observed that during the time of loading the RDB file, many nodes (master and slave), the key count goes to '0' and increases until the RDB file loads completely. This happens during the time between the following log statements.
|
that's normal, the replica flushes it's data before loading the new data. |
Redis crashes with the following logs on multiple nodes (at different times). What could be the reason for the same. Please let me know if you need any details to be collected. Thanks!
Please keep in mind that this issue tracker should be used for reporting bugs or proposing improvements to the Redis server.
Generally, questions about using Redis should be directed to the community:
redis
tag at StackOverflowIt is also possible that your question was already asked here, so please do a quick issues search before submitting. Lastly, if your question is about one of Redis' clients, you may to contact your client's developers for help.
That said, please feel free to replace all this with your question :)
The text was updated successfully, but these errors were encountered: