THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Currently, the different artifacts are cleaned up in different locations:
Component | Who is responsible? | Why? |
|
| It needs to work without a |
|
| We need to be able to fetch a |
|
| We can clean this up after there won’t be any more contenders. |
|
| |
|
| This is tied to a single job execution (JobMasterLifecycle). |
|
|
|
The plan is to provide a common interface that enables all components to trigger the cleanup based on the JobID. This cleanup component can encapsulate the retry mechanism. The actual cleanup can then be triggered either in the JobMaster or the Dispatcher depending on whether a JobGraph is still available or not.
...
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...