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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: