Open hwware opened 2 months ago
Is it starvation of the cluster bus?
Maybe something like dual channel sync can help? Rdb in fork process so main process can still talk to cluster bus...
the linked referenced issue also has a proposed open PR to attempt to fix the issue https://github.com/redis/redis/pull/13308
basically the redis inbound cluster connection tcp keepalive idle time was set to 2 * cluster node timeout, which typically people set to quite agggressive values (seconds). and tcp keepalive idle interval is set to 1/3 of idle time right now.
https://github.com/valkey-io/valkey/blob/unstable/src/cluster_legacy.c#L1412
so the PR makes the tcp keepalive settings of the redis inbound cluster connection to be configurable by the existing config variable server.tcpkeepalive (same as other redis server connection).
Describe the bug
Reference: Redis issue https://github.com/redis/redis/issues/12001 Since Redis PR https://github.com/redis/redis/pull/11785 is involved, once one single node data more than 7GB, replica node can not sync with primary node.
To reproduce
Reference from Redis issue https://github.com/redis/redis/issues/12001 and link https://github.com/redis/redis/issues/12001#issuecomment-1743066121
Expected behavior
Replica node could sync with primary node
Additional information
Any additional information that is relevant to the problem.