Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Admin] Zookeeper lock report #2136

Open
mreyescdl opened this issue Dec 17, 2024 · 0 comments
Open

[Admin] Zookeeper lock report #2136

mreyescdl opened this issue Dec 17, 2024 · 0 comments
Assignees

Comments

@mreyescdl
Copy link
Contributor

The current issue with zookeeper clients encountering errors from the server result in states that are not failed, but left in an unfinished state.
These entries are locked so that no Daemon process will finish the work.

Currently, there is no reliable way to determine that these jobs are not active.

One way to determine an inactive job is to check the lock creation date. If more than 12 hours old, then it is a very long running submission or it is stale due to Zookeeper error.

A lock report from the Admin tool could aid in this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants