Closed kazysgurskas closed 1 year ago
There are often situations where after a node restart or crash, it starts a full SYNC from the master and is blocking client writes (but not reads) with error LOADING Redis is loading the dataset in memory. I think the most usual scenario to use KeyDB on k8s is to have active-replica enabled, so all nodes accept writes, therefore it should be good to avoid client errors when the node is in LOAD state. ref: https://community.keydb.dev/t/active-replica-loading-redis-is-loading-the-dataset-in-memory-on-full-sync/137 https://github.com/Snapchat/KeyDB/issues/365
LOADING Redis is loading the dataset in memory
There are often situations where after a node restart or crash, it starts a full SYNC from the master and is blocking client writes (but not reads) with error
LOADING Redis is loading the dataset in memory. I think the most usual scenario to use KeyDB on k8s is to have active-replica enabled, so all nodes accept writes, therefore it should be good to avoid client errors when the node is in LOAD state. ref: https://community.keydb.dev/t/active-replica-loading-redis-is-loading-the-dataset-in-memory-on-full-sync/137 https://github.com/Snapchat/KeyDB/issues/365