You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
ERROR Error 1213: Deadlock found when trying to get lock; try restarting transaction ERROR ExpireAvailableNodes: failed to remove old entries: Error 1213: Deadlock found when trying to get lock; try restarting transaction
#1510
Open
Hironerd opened this issue
Sep 29, 2024
· 0 comments
In the single-node and three-node raft high availability orchestrator I deployed, errors appeared in the logs. What is the reason?And how can I avoid this problem?
Errors like this:
2024-09-29 02:55:48 ERROR Error 1213: Deadlock found when trying to get lock; try restarting transaction
2024-09-29 02:55:48 ERROR ExpireAvailableNodes: failed to remove old entries: Error 1213: Deadlock found when trying to get lock; try restarting transaction
The text was updated successfully, but these errors were encountered:
Hironerd
changed the title
ERROR Error 1213: Deadlock found when trying to get lock; try restarting transaction
ERROR Error 1213: Deadlock found when trying to get lock; try restarting transaction ERROR ExpireAvailableNodes: failed to remove old entries: Error 1213: Deadlock found when trying to get lock; try restarting transaction
Sep 29, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the single-node and three-node raft high availability orchestrator I deployed, errors appeared in the logs. What is the reason?And how can I avoid this problem?
Errors like this:
2024-09-29 02:55:48 ERROR Error 1213: Deadlock found when trying to get lock; try restarting transaction
2024-09-29 02:55:48 ERROR ExpireAvailableNodes: failed to remove old entries: Error 1213: Deadlock found when trying to get lock; try restarting transaction
The text was updated successfully, but these errors were encountered: