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
7578:7598:S 31 Mar 2023 08:44:47.008 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '4c21ed6eb1a72855461f1298444bae8cef804073', my replication IDs are 'e50cd6c93bf5ed0635d3c9b55f5fe7b2b8b05f2b' and '0000000000000000000000000000000000000000')
7578:7598:S 31 Mar 2023 08:44:47.008 * Delay next BGSAVE for diskless SYNC
7578:7598:S 31 Mar 2023 08:44:49.144 - DB 0: 15091496 keys (15091459 volatile) in 16777216 slots HT.
7578:7598:S 31 Mar 2023 08:44:49.145 . 2 clients connected (1 replicas), 2199275328 bytes in use
7578:7598:S 31 Mar 2023 08:44:52.160 * Starting BGSAVE for SYNC with target: replicas sockets
7578:7598:S 31 Mar 2023 08:44:52.184 * Background RDB transfer started
7578:8020:S 31 Mar 2023 08:44:52.203 - RDB: 2290 MB of memory used by copy-on-write
7578:8020:S 31 Mar 2023 08:44:54.224 - RDB: 2395 MB of memory used by copy-on-write
7578:7598:S 31 Mar 2023 08:44:54.256 - DB 0: 15091496 keys (15091459 volatile) in 4 slots HT.
7578:7598:S 31 Mar 2023 08:44:54.256 . 2 clients connected (1 replicas), 2329470016 bytes in use
7578:8020:S 31 Mar 2023 08:44:57.234 - RDB: 2555 MB of memory used by copy-on-write
7578:7598:S 31 Mar 2023 08:44:59.446 - DB 0: 15091496 keys (15091459 volatile) in 4 slots HT.
7578:7598:S 31 Mar 2023 08:44:59.446 . 2 clients connected (1 replicas), 2554825808 bytes in use
7578:8020:S 31 Mar 2023 08:45:00.240 - RDB: 2637 MB of memory used by copy-on-write
7578:8020:S 31 Mar 2023 08:45:03.419 - RDB: 2690 MB of memory used by copy-on-write
^C
The text was updated successfully, but these errors were encountered:
I experience this too. However I found that the problem seemed related to an excessive growth in open file-descriptors. Once the server got to around 11K-12K open, the process would hang. Therefore I'm wondering if it is solved by this #579
Describe the bug
I'm running a pair of KeyDB servers in active-replica mode. When restarting one of the node it cannot be synced with the other.
To reproduce
Expected behavior
Two nodes are in-sync.
Additional information
Configuration:
Info:
Here is the log:
7578:7598:S 31 Mar 2023 08:44:47.008 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '4c21ed6eb1a72855461f1298444bae8cef804073', my replication IDs are 'e50cd6c93bf5ed0635d3c9b55f5fe7b2b8b05f2b' and '0000000000000000000000000000000000000000')
7578:7598:S 31 Mar 2023 08:44:47.008 * Delay next BGSAVE for diskless SYNC
7578:7598:S 31 Mar 2023 08:44:49.144 - DB 0: 15091496 keys (15091459 volatile) in 16777216 slots HT.
7578:7598:S 31 Mar 2023 08:44:49.145 . 2 clients connected (1 replicas), 2199275328 bytes in use
7578:7598:S 31 Mar 2023 08:44:52.160 * Starting BGSAVE for SYNC with target: replicas sockets
7578:7598:S 31 Mar 2023 08:44:52.184 * Background RDB transfer started
7578:8020:S 31 Mar 2023 08:44:52.203 - RDB: 2290 MB of memory used by copy-on-write
7578:8020:S 31 Mar 2023 08:44:54.224 - RDB: 2395 MB of memory used by copy-on-write
7578:7598:S 31 Mar 2023 08:44:54.256 - DB 0: 15091496 keys (15091459 volatile) in 4 slots HT.
7578:7598:S 31 Mar 2023 08:44:54.256 . 2 clients connected (1 replicas), 2329470016 bytes in use
7578:8020:S 31 Mar 2023 08:44:57.234 - RDB: 2555 MB of memory used by copy-on-write
7578:7598:S 31 Mar 2023 08:44:59.446 - DB 0: 15091496 keys (15091459 volatile) in 4 slots HT.
7578:7598:S 31 Mar 2023 08:44:59.446 . 2 clients connected (1 replicas), 2554825808 bytes in use
7578:8020:S 31 Mar 2023 08:45:00.240 - RDB: 2637 MB of memory used by copy-on-write
7578:8020:S 31 Mar 2023 08:45:03.419 - RDB: 2690 MB of memory used by copy-on-write
^C
The text was updated successfully, but these errors were encountered: