[jira] [Updated] (YARN-6231) TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on branch-2

2017-02-27 Thread Arun Suresh (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Suresh updated YARN-6231:
--

+1.. The latest patch looks good.. Thanks karthik




> TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on 
> branch-2 
> ---
>
> Key: YARN-6231
> URL: https://issues.apache.org/jira/browse/YARN-6231
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.9.0
>Reporter: Arun Suresh
>Assignee: Karthik Kambatla
> Attachments: YARN-6231.001.patch, YARN-6231.002.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Updated] (YARN-6231) TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on branch-2

2017-02-25 Thread Karthik Kambatla (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karthik Kambatla updated YARN-6231:
---
Attachment: YARN-6231.002.patch

Actually, a better approach might be to call {{scheduler.update()}} right after 
the {{scheduler.allocate()}} calls in {{FairSchedulerTestBase}}. That should 
take care of other similar test failures. 

> TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on 
> branch-2 
> ---
>
> Key: YARN-6231
> URL: https://issues.apache.org/jira/browse/YARN-6231
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.9.0
>Reporter: Arun Suresh
>Assignee: Karthik Kambatla
> Attachments: YARN-6231.001.patch, YARN-6231.002.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

[jira] [Updated] (YARN-6231) TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on branch-2

2017-02-25 Thread Karthik Kambatla (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karthik Kambatla updated YARN-6231:
---
Attachment: YARN-6231.001.patch

Yeah, looks like some recent change has exposed a timing issue. 

Attached is a patch that seems to fix it. Ran 250 runs with the patch without 
failure; without the patch it fails in less than 10 runs. 

> TestFairScheduler::testMoveWouldViolateMaxResourcesConstraints failing on 
> branch-2 
> ---
>
> Key: YARN-6231
> URL: https://issues.apache.org/jira/browse/YARN-6231
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.9.0
>Reporter: Arun Suresh
>Assignee: Karthik Kambatla
> Attachments: YARN-6231.001.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org