You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2015/12/20 15:08:46 UTC

[jira] [Commented] (AURORA-1183) job stay in PENDING: Host drained for maintenance, even though host is ACTIVE

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

Stephan Erb commented on AURORA-1183:
-------------------------------------

Any update on this one? Is this still an issue or can we mark as resolved?

> job stay in PENDING: Host drained for maintenance, even though host is ACTIVE
> -----------------------------------------------------------------------------
>
>                 Key: AURORA-1183
>                 URL: https://issues.apache.org/jira/browse/AURORA-1183
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>    Affects Versions: 0.7.0
>            Reporter: Bhuvan Arumugam
>
> Example: 1. I schedule a job with 1 instance, 1 cpu and pin the job to specific host, the job stay in {{PENDING: Insufficient CPU}} state, if there is >1 cpu in the offer. It's expected.
> Example: 2. I schedule a job with 2 instances, 1 cpu each and pin the job to specific hosts; one instance is scheduled/running. The other instance remain in {{PENDING: Host drained for maintenance}} state, if there is >1 cpu in the offer for this slave.
> The error message in example 2 is incorrect. It should indicate that job is PENDING due to insufficient CPU.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)