So, I assume that you checked in the configuration file of the slave that the RDB was deactivated (all saved lines are commented out) and the slave was restarted after changing the configuration file (so that this configuration is active).
At this moment, the background reset operation of the slave is deactivated, but this does not prevent the slave from writing the dump file. In fact, the subordinate should write the dump file during startup: in this way, it extracts data from the master in bulk.
When the slave starts up, it sends a SYNC request to the host:
- The wizard begins to accumulate Redis teams.
- The wizard resets the background
- Master sends the dump file to slave mode in bulk mode
- The slave reads the dump file from the master and writes it to disk
- When it is complete, the slave will load the dump file from disk
- Slave begins processing Redis commands accumulated by the master
- In the end, the subordinate will catch up
- Slave synchronizes with master
This is why you can find dump files on the slave, even if RDB is deactivated for slaves.
source share