.lock
in the root of the repository.
The lock file contains a UUID that is generated when the lock is acquired.
Each time on startup, ConfigSync checks if the lock file exists in the repository and the file contents match the UUID
in the config-sync.branch-lock
Fusion configuration property (stored in ZooKeeper).
- If the lock file does not exist, ConfigSync creates it and writes the UUID to the file.
- If the Fusion configuration property is not set, ConfigSync sets the UUID in the
config-sync.branch-lock
property to the UUID in the lock file. - If the lock file exists and the UUID in the file matches the UUID in the
config-sync.branch-lock
Fusion configuration, ConfigSync continues to work with the repository; otherwise it fails to start.
App lock <SOME-UUID> doesn’t match git lock <SOME-OTHER-UUID>
, see Delete the ConfigSync lock file.
Delete the ConfigSync lock file
Delete the ConfigSync lock file
If you recreate a Fusion cluster, the lock file remains in the repository and prevents ConfigSync from starting.
You might see the following error in the logs:To resolve this issue:
-
Delete the lock file.
The lock is a file named
.lock
in the root of the repository. -
Restart the
config-sync
service.
Learn more
Lock ConfigSync to one commit
Lock ConfigSync to one commit
ConfigSync can lock the configuration to a specific commit.This means that ConfigSync :Replace
- Does not apply any commits that are newer than the locked commit
- Does not update changes from the Fusion cluster to the Git repository
locked-commit
using the API:request
COMMIT_SHA1
with the commit SHA1 to which you want to lock ConfigSync.If
locked-commit
precedes latest-synced-commit
, ConfigSync reverts all changes to the locked-commit
and sets latest-synced-commit
to locked-commit
.