Details
-
Bug
-
Status: Accepted
-
Major
-
Resolution: Unresolved
-
0.25.0
-
None
-
None
Description
gabriel.hartmann@gmail.com recently noticed that his custom executor was getting killed by master when multiple tasks attempt to use persistent volumes with the same container_path. A CREATE operation that created two persistent volumes with the same container_path succeeded, and a subsequent offer included those persistent volumes. Then tasks were launched on a single executor that used these volumes, and at that point the master killed the executor. Better behavior might be for the first task to launch successfully, with the second task returning TASK_FAILED with an appropriate reason and message.