Ensure RaftStore lock files are created and updated atomically #10681
Labels
kind/bug
Categorizes an issue or PR as a bug
severity/high
Marks a bug as having a noticeable impact on the user with no known workaround
version:8.1.1
Marks an issue as being completely or in parts released in 8.1.1
version:8.2.0-alpha1
Marks an issue as being completely or in parts released in 8.2.0-alpha1
version:8.2.0
Marks an issue as being completely or in parts released in 8.2.0
Describe the bug
We observed that on startup the lock file is empty, and this failed the startup of the partition with "Failed to acquire lock".
Possible reasons:
Workaround in this case is to delete the lock file and restart the pod. This is risky, because lock file exists to ensure that the directories are not shared by multiple pods. If we workaround it, we have to manually check if everything is configured correctly.
Expected behavior
The lock is not empty. Either lock file exists and have contents, or lock file does not exist.
Environment:
The text was updated successfully, but these errors were encountered: