mirror of
https://github.com/clusterio/clusterio.git
synced 2026-11-17 23:33:12 +09:00
Invalidate instance copies when player data is imported or deleted
Generations alone could not order a repair against copies held by instances. Deleting dropped the watermark, so a stale instance could skip downloading the new baseline. An import could land on the same generation as an upload that never reached the controller, and the instance would then keep its own copy. Imports and deletes now bump a per-player epoch, which the controller returns on acquire and checks on upload. Instances throw away a copy from an earlier epoch, and deleted players keep their generation and epoch in player_sync_deleted.json. A restarted download also takes the new generation instead of the outdated one. Generations in player data must now be non-negative integers, so an invalid import is refused before it reaches the datastore. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
1d14148606
commit
f12b016cec
9 files changed
+159
-39
No files matched your search
@@ -45,8 +45,11 @@ The same operations are available from clusterioctl:
|
||||
npx clusterioctl player-sync delete <player>
|
||||
npx clusterioctl player-sync release <player>
|
||||
|
||||
Importing bumps the generation so instances holding an older copy download the new one the next time the player joins.
|
||||
Deleting makes the next join turn whatever the player has on that instance into the new synced inventory.
|
||||
Importing and deleting both start a new epoch for the player.
|
||||
An instance holding a copy from an earlier epoch throws it away the next time the player joins, even if it is newer than what the controller has, and an upload from an earlier epoch is discarded.
|
||||
After an import the instance downloads the new data.
|
||||
After a delete the next join turns whatever the player has on that instance into the new synced inventory.
|
||||
Deleted players stay listed in `player_sync_deleted.json` in the database directory so their epoch survives a controller restart.
|
||||
Both are refused while an instance holds the lock on the player, because the instance uploads its own copy when the player leaves and that would undo the change.
|
||||
Have the player leave first, or release the lock if the instance is stuck holding it.
|
||||
|
||||
|
||||
Reference in new issue
Block a user