-
Notifications
You must be signed in to change notification settings - Fork 9.2k
YARN-11835 DockerContainerDeletionTask did not clear tasks in leveldb #7811
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
Conversation
YARN-11835 DockerContainerDeletionTask did not clear tasks in leveldb
|
💔 -1 overall
This message was automatically generated. |
| LinuxContainerExecutor exec = ((LinuxContainerExecutor) | ||
| getDeletionService().getContainerExecutor()); | ||
| exec.removeDockerContainer(containerId); | ||
| deletionTaskFinished(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is make sense for deletion,I'm wondering if I need to set the status of the deletionTask after removeDockerContainer fails
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have considered it more thoroughly, so that there is still a chance to clean it up again after the deletion fails.
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
YARN-11835 DockerContainerDeletionTask did not clear tasks in leveldb
Description of PR
DockerContainerDeletionTask did not clear tasks in leveldb, which can result in tasks that were expected to be cleared remaining in leveldb. Each time the nodemanager is restarted, the corresponding deletion task is triggered
How was this patch tested?
Tested in our own production environment and passed