Details
-
Bug
-
Status: Reviewable
-
Critical
-
Resolution: Unresolved
-
1.4.0
-
None
-
None
Description
I was running a job which uses GPUs. It runs fine most of the time.
But occasionally I see the following message in the mesos log.
"Collect failed: Requested 1 but only 0 available"
Followed by executor getting killed and the tasks getting lost. This happens even before the the job starts. A little search in the code base points me to something related to GPU resource being the probable cause.
There is no deterministic way that this can be reproduced. It happens occasionally.
I have attached the slave log for the issue.
Using 1.4.0 Mesos Master and 1.4.0 Mesos Slave.
Attachments
Attachments
Issue Links
- is duplicated by
-
MESOS-10119 failure to destroy container can cause the agent to "leak" a GPU
- Resolved