In den Logs sieht das so aus.
Master 855:M 10 May 2020 07:51:45.458 * DB loaded from disk: 0.563 seconds 855:M 10 May 2020 07:51:45.458 * Ready to accept connections 855:M 10 May 2020 07:51:45.713 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:51:45.713 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'd6042ec68cc9b4e3ccd8ebd8e28012133c24efb4', my replication IDs are '071743$ 855:M 10 May 2020 07:51:45.713 * Starting BGSAVE for SYNC with target: disk 855:M 10 May 2020 07:51:45.716 * Background saving started by pid 859 859:C 10 May 2020 07:51:46.107 * DB saved on disk 859:C 10 May 2020 07:51:46.111 * RDB: 24 MB of memory used by copy-on-write 855:M 10 May 2020 07:51:46.162 * Background saving terminated with success 855:M 10 May 2020 07:51:46.324 * Synchronization with replica 10.0.0.2:6379 succeeded 855:M 10 May 2020 07:51:50.674 # Connection with replica 10.0.0.2:6379 lost. 855:M 10 May 2020 07:51:51.254 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:51:51.255 * Partial resynchronization request from 10.0.0.2:6379 accepted. Sending 0 bytes of backlog starting from offset 1. 855:M 10 May 2020 07:56:47.021 * 10 changes in 300 seconds. Saving... 855:M 10 May 2020 07:56:47.023 * Background saving started by pid 978 978:C 10 May 2020 07:56:47.426 * DB saved on disk 978:C 10 May 2020 07:56:47.428 * RDB: 28 MB of memory used by copy-on-write 855:M 10 May 2020 07:56:47.529 * Background saving terminated with success 855:M 10 May 2020 07:56:52.961 # Connection with replica 10.0.0.2:6379 lost. 855:M 10 May 2020 07:56:53.649 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:56:53.649 * Partial resynchronization request from 10.0.0.2:6379 accepted. Sending 0 bytes of backlog starting from offset 6413. 855:M 10 May 2020 08:01:48.089 * 10 changes in 300 seconds. Saving... 855:M 10 May 2020 08:01:48.091 * Background saving started by pid 1044 1044:C 10 May 2020 08:01:48.502 * DB saved on disk 1044:C 10 May 2020 08:01:48.505 * RDB: 24 MB of memory used by copy-on-write 855:M 10 May 2020 08:01:48.594 * Background saving terminated with success Slave 1324:S 10 May 2020 07:56:53.651 * DB loaded from disk: 0.638 seconds 1324:S 10 May 2020 07:56:53.651 * Before turning into a replica, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partia$ 1324:S 10 May 2020 07:56:53.651 * Ready to accept connections 1324:S 10 May 2020 07:56:53.651 * Connecting to MASTER 10.0.0.4:6379 1324:S 10 May 2020 07:56:53.651 * MASTER <-> REPLICA sync started 1324:S 10 May 2020 07:56:53.652 * Non blocking connect for SYNC fired the event. 1324:S 10 May 2020 07:56:53.653 * Master replied to PING, replication can continue... 1324:S 10 May 2020 07:56:53.654 * Trying a partial resynchronization (request 86ba864a2575c203a4eddd80bd6f4b058ebe1fb7:6413). 1324:S 10 May 2020 07:56:53.655 * Successful partial resynchronization with master. 1324:S 10 May 2020 07:56:53.655 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 1324:S 10 May 2020 08:01:54.077 * 10 changes in 300 seconds. Saving... 1324:S 10 May 2020 08:01:54.080 * Background saving started by pid 1494 1494:C 10 May 2020 08:01:54.523 * DB saved on disk 1494:C 10 May 2020 08:01:54.527 * RDB: 0 MB of memory used by copy-on-write 1324:S 10 May 2020 08:01:54.582 * Background saving terminated with successRedis oder MongoDB?
-
Ich hatte mich bei meiner damaligen Installation für Redis entschieden, diese DB hält die Daten im Speicher vor. Sollte das mal in Zukunft ein Problem werden, wenn ich mal 100000 User habe
, dann bräuchte man evt. mal ein Tool um die Redis Datenbank in eine MongoDB zu migrieren.Hier ist so ein Tool https://github.com/BenLubar/nodebb-postgres-converter
Thread zum Thema https://community.nodebb.org/topic/7286/redis-or-mongodb