[ 
https://issues.apache.org/jira/browse/MESOS-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523051#comment-16523051
 ] 

Benjamin Mahler commented on MESOS-8038:
----------------------------------------

[~zhitao] please attach logs.

w.r.t. to how to handle failures in the containerization code, I would expect 
that to be something the containerization working group enforces some 
consistency around. When I looked into this issue, I didn't see how it could be 
gpu isolation specific. I think it’s a higher level bug in the 
agent/containerizer interaction (e.g. letting resources get offered in the 
master before the container shrink finishes). Was there anything interesting 
before it happened, like agent re-registration or gpu tasks finishing?

> Launching GPU task sporadically fails.
> --------------------------------------
>
>                 Key: MESOS-8038
>                 URL: https://issues.apache.org/jira/browse/MESOS-8038
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation, containerization, gpu
>    Affects Versions: 1.4.0
>            Reporter: Sai Teja Ranuva
>            Assignee: Zhitao Li
>            Priority: Critical
>         Attachments: mesos-master.log, mesos-slave.INFO.log
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to