In servers, save-off does not disable autosaving and autosaves continue to happen at 5 minute intervals. This is catastrophic for backup scripts which have no choice but to rely on the save-off functionality to capture a consistent world state.
Steps to reproduce:
Launch a new Minecraft server and wait for the world to generate
Run
save-offin the console and note the timeWait 5 minutes
Notice that the file modify time for
world/level.datis a time after the timesave-offwas run and continues to be updated every 5 minutes
This is different from MC-4417 because the autosave continues happening, even occurring multiple times after the save-off command is run. This is not simply an issue of waiting for a single save to finish.
This is different from MC-3208 because this has nothing to do with the /stop command.
Linked issues
Comments 2
Re: Mark Derickson
I disagree. In MC-3208 it says: "When the server is stopped, player positions and the world are saved." This makes it clear that MC-3208 is related to the behavior of the stop command when auto-saving is turned off. It does not mention that the saves continue to occur every five minutes even before the server is stopped.
Hello! I still think that this is a duplicate of MC-3208. If I understand MC-3208 correctly, using the /stop command is just a way to prove that auto-saving is not occurring.