[jira] [Comment Edited] (MESOS-8038) Launching GPU task sporadically fails.

["Sai Teja Ranuva (JIRA)" <ji...@apache.org>]

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

Sai Teja Ranuva edited comment on MESOS-8038 at 10/5/17 3:35 PM:
-----------------------------------------------------------------

[~bmahler] Attached the logs for master and slave. 
For more context, when a large number of tasks (10-20) are launched, this problem occurs always.
When the framework launches job, with lesser number of tasks(1-6), it works fine or occurs very rarely. All the tasks are gpu based.


was (Author: saitejar):
[~bmahler] Attached the logs for master and slave. 

> Launching GPU task sporadically fails.
> --------------------------------------
>
>                 Key: MESOS-8038
>                 URL: https://issues.apache.org/jira/browse/MESOS-8038
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation, gpu
>    Affects Versions: 1.4.0
>            Reporter: Sai Teja Ranuva
>            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
(v6.4.14#64029)