[jira] [Commented] (YARN-1901) All tasks restart during RM failover on Hive

2014-04-04 Thread Fengdong Yu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13959815#comment-13959815 ] Fengdong Yu commented on YARN-1901: --- Hi [~oazwa], Can you search the mail list of

[jira] [Created] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

2014-04-04 Thread Sietse T. Au (JIRA)
Sietse T. Au created YARN-1902: -- Summary: Allocation of too many containers when a second request is done with the same resource capability Key: YARN-1902 URL: https://issues.apache.org/jira/browse/YARN-1902

[jira] [Commented] (YARN-1901) All tasks restart during RM failover on Hive

2014-04-04 Thread Jason Lowe (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960026#comment-13960026 ] Jason Lowe commented on YARN-1901: -- This appears to be a duplicate of HIVE-6638. As

[jira] [Updated] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

2014-04-04 Thread Sietse T. Au (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sietse T. Au updated YARN-1902: --- Attachment: YARN-1902.patch Allocation of too many containers when a second request is done with the

[jira] [Updated] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

2014-04-04 Thread Sietse T. Au (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sietse T. Au updated YARN-1902: --- Description: Regarding AMRMClientImpl Scenario 1: Given a ContainerRequest x with Resource y, when

[jira] [Updated] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

2014-04-04 Thread Sietse T. Au (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sietse T. Au updated YARN-1902: --- Description: Regarding AMRMClientImpl Scenario 1: Given a ContainerRequest x with Resource y, when

[jira] [Commented] (YARN-1837) TestMoveApplication.testMoveRejectedByScheduler randomly fails

2014-04-04 Thread Jian He (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960255#comment-13960255 ] Jian He commented on YARN-1837: --- looks good to me, +1

[jira] [Commented] (YARN-1837) TestMoveApplication.testMoveRejectedByScheduler randomly fails

2014-04-04 Thread Jian He (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960259#comment-13960259 ] Jian He commented on YARN-1837: --- One more observation is that move is allowed at submitted

[jira] [Commented] (YARN-1837) TestMoveApplication.testMoveRejectedByScheduler randomly fails

2014-04-04 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960281#comment-13960281 ] Hudson commented on YARN-1837: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5458 (See

[jira] [Updated] (YARN-1872) TestDistributedShell occasionally fails in trunk

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1872: -- Priority: Blocker (was: Major) Target Version/s: 2.4.1 Labels: (was: patch)

[jira] [Commented] (YARN-1872) TestDistributedShell occasionally fails in trunk

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960357#comment-13960357 ] Zhijie Shen commented on YARN-1872: --- bq. After the DistributedShell AM requested

[jira] [Created] (YARN-1903) TestNMClient fails occasionally

2014-04-04 Thread Zhijie Shen (JIRA)
Zhijie Shen created YARN-1903: - Summary: TestNMClient fails occasionally Key: YARN-1903 URL: https://issues.apache.org/jira/browse/YARN-1903 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-1903) TestNMClient fails occasionally

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960418#comment-13960418 ] Zhijie Shen commented on YARN-1903: --- I found the following log: {code} 2014-04-04

[jira] [Commented] (YARN-1903) TestNMClient fails occasionally

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960480#comment-13960480 ] Zhijie Shen commented on YARN-1903: --- I did more investigation. Instead of a test failure,

[jira] [Updated] (YARN-1903) Killing Container on NEW and LOCALIZING will result in exitCode and diagnostics not set

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1903: -- Summary: Killing Container on NEW and LOCALIZING will result in exitCode and diagnostics not set (was:

[jira] [Commented] (YARN-1901) All tasks restart during RM failover on Hive

2014-04-04 Thread Fengdong Yu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960515#comment-13960515 ] Fengdong Yu commented on YARN-1901: --- Yes, exactly duplicated, thanks, I've closed it.

[jira] [Updated] (YARN-1903) Killing Container on NEW and LOCALIZING will result in exitCode and diagnostics not set

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1903: -- Attachment: YARN-1903.1.patch Upload a patch to fix these issues Killing Container on NEW and

[jira] [Resolved] (YARN-1901) All tasks restart during RM failover on Hive

2014-04-04 Thread Fengdong Yu (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fengdong Yu resolved YARN-1901. --- Resolution: Duplicate All tasks restart during RM failover on Hive

[jira] [Updated] (YARN-1898) Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

2014-04-04 Thread Xuan Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1898: Attachment: YARN-1898.addendum.patch submit the same patch again to kill off the Jenkins Standby RM's

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

2014-04-04 Thread Jason Lowe (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960541#comment-13960541 ] Jason Lowe commented on YARN-1769: -- The patch no longer applies cleanly after YARN-1512.

[jira] [Commented] (YARN-1903) Killing Container on NEW and LOCALIZING will result in exitCode and diagnostics not set

2014-04-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960776#comment-13960776 ] Hadoop QA commented on YARN-1903: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1872) TestDistributedShell occasionally fails in trunk

2014-04-04 Thread Hong Zhiguo (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960797#comment-13960797 ] Hong Zhiguo commented on YARN-1872: --- Yes. It is. And MapRedue V2 AM contains some code to

[jira] [Commented] (YARN-1903) Killing Container on NEW and LOCALIZING will result in exitCode and diagnostics not set

2014-04-04 Thread Xuan Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960809#comment-13960809 ] Xuan Gong commented on YARN-1903: - +1 LGTM Also, I run the TestNMClient with this patch

[jira] [Commented] (YARN-1898) Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

2014-04-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960826#comment-13960826 ] Hadoop QA commented on YARN-1898: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1878) Yarn standby RM taking long to transition to active

2014-04-04 Thread Arun C Murthy (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960929#comment-13960929 ] Arun C Murthy commented on YARN-1878: - [~xgong] is this ready to go? Let's get this

[jira] [Updated] (YARN-1878) Yarn standby RM taking long to transition to active

2014-04-04 Thread Arun C Murthy (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1878: Target Version/s: 2.4.1 Yarn standby RM taking long to transition to active

[jira] [Updated] (YARN-1878) Yarn standby RM taking long to transition to active

2014-04-04 Thread Arun C Murthy (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1878: Priority: Blocker (was: Major) Yarn standby RM taking long to transition to active

[jira] [Commented] (YARN-1898) Standby RM's conf, stacks, logLevel, metrics, jmx and logs links are redirecting to Active RM

2014-04-04 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960941#comment-13960941 ] Hudson commented on YARN-1898: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5460 (See

[jira] [Updated] (YARN-1701) More intuitive defaults for AHS

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1701: -- Affects Version/s: (was: 2.4.0) 2.4.1 More intuitive defaults for AHS

[jira] [Commented] (YARN-1701) More intuitive defaults for AHS

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960967#comment-13960967 ] Zhijie Shen commented on YARN-1701: --- [~jira.shegalov], would you mind updating the patch?

[jira] [Updated] (YARN-1701) Improve default paths of timeline store and generic history store

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1701: -- Issue Type: Bug (was: Sub-task) Parent: (was: YARN-321) Improve default paths of timeline

[jira] [Updated] (YARN-1701) Improve default paths of timeline store and generic history store

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1701: -- Summary: Improve default paths of timeline store and generic history store (was: More intuitive

[jira] [Created] (YARN-1904) Uniform the XXXXNotFound messages from ClientRMService and ApplicationHistoryClientService

2014-04-04 Thread Zhijie Shen (JIRA)
Zhijie Shen created YARN-1904: - Summary: Uniform the NotFound messages from ClientRMService and ApplicationHistoryClientService Key: YARN-1904 URL: https://issues.apache.org/jira/browse/YARN-1904

[jira] [Updated] (YARN-1904) Uniform the XXXXNotFound messages from ClientRMService and ApplicationHistoryClientService

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1904: -- Attachment: YARN-1904.1.patch Create a patch, simple message editing, without new test cases Uniform

[jira] [Updated] (YARN-1904) Uniform the XXXXNotFound messages from ClientRMService and ApplicationHistoryClientService

2014-04-04 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1904: -- Target Version/s: 2.4.1 Uniform the NotFound messages from ClientRMService and

[jira] [Commented] (YARN-1904) Uniform the XXXXNotFound messages from ClientRMService and ApplicationHistoryClientService

2014-04-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960988#comment-13960988 ] Hadoop QA commented on YARN-1904: - {color:red}-1 overall{color}. Here are the results of