Our replication mechanism is based on the journal updates.

In most cases, every command set/update/delete key is added into the journal via Transaction::LogAutoJournalOnShard() call at the end of the transaction; in other cases, it is a direct RecordJournal() call in the command.

Problem: During loading data via the DFLY LOAD command, we write keys directly into the db_slice without journaling them, and because the replica is in the STABLE_SYNC phase, we track only journal updates.

Possible solutions:

• restart the replication process, it will trigger FULL SYNC, so all data in the db_slices will be replicated
• add explicit recording data into the journal during RDB loading