[jira] [Commented] (YARN-1468) TestRMRestart.testRMRestartWaitForPreviousAMToFinish get failed.

[ https://issues.apache.org/jira/browse/YARN-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310976#comment-15310976 ] Eric Badger commented on YARN-1468: --- [~mitdesai], I saw this test failing in the same way that you

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141736#comment-15141736 ] Eric Badger commented on YARN-4686: --- Moving to YARN project, since this affects the MiniYarnCluster. >

[jira] [Moved] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger moved MAPREDUCE-6507 to YARN-4686: -- Assignee: (was: Eric Badger) Target Version/s: 2.7.3

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169686#comment-15169686 ] Eric Badger commented on YARN-4686: --- TestYarnCLI, TestAMRMClient, TestYarnClient, TestNMClient, and

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.001.patch Transition 1 RM to active in MiniYarnCluster start. Also improve

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15169624#comment-15169624 ] Eric Badger commented on YARN-4686: --- I am unable to reproduce any of the JUnit timeout failures

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199736#comment-15199736 ] Eric Badger commented on YARN-4686: --- [~kasha] When HA is not enabled, the RM will be transitioned to

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.005.patch I moved the total capacity check out of the waitForNodeManagersToConnect

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.006.patch [~eepayne] good catch! I've switched that line in the comment in this

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Target Version/s: 3.0.0, 2.8.0, 2.7.3 (was: 2.7.3) > MiniYARNCluster.start() returns before cluster is

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15194235#comment-15194235 ] Eric Badger commented on YARN-4686: --- As per my comment above: TestYarnCLI, TestAMRMClient,

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686-branch-2.7.006.patch [~eepayne] Attaching the branch-2.7 patch. It passed all of

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15191211#comment-15191211 ] Eric Badger commented on YARN-4686: --- Thanks for finding this failure, [~eepayne]. I narrowed down the

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.004.patch The new patch changes the waitForNodeManagersToConnect method in

[jira] [Commented] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15228520#comment-15228520 ] Eric Badger commented on YARN-4756: --- [~kasha], does my explanation make sense? Do you have any other

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.003.patch [~kasha], I wasn't clear in my original text. The patches in [YARN-4686]

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.005.patch Removing irrelevant changes from patch. > Unnecessary wait in Node

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686-branch-2.7.007.patch Attaching branch-2.7 patch after rebase. Must not have done

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204435#comment-15204435 ] Eric Badger commented on YARN-4686: --- Thanks, [~eepayne]! > MiniYARNCluster.start() returns before

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: (was: YARN-4686-branch-2.7.007.patch) > MiniYARNCluster.start() returns before cluster

[jira] [Commented] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204875#comment-15204875 ] Eric Badger commented on YARN-4756: --- [~eepayne], [~jlowe], [~kasha], can one of you review this patch

[jira] [Assigned] (YARN-4760) proxy redirect to history server uses wrong URL

[ https://issues.apache.org/jira/browse/YARN-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned YARN-4760: - Assignee: Eric Badger > proxy redirect to history server uses wrong URL >

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.002.patch This patch fixes a race issue between the NMs resyncing with the RM and

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.003.patch Fixing a deadlock issue related to the Node Status Updater thread and

[jira] [Created] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

Eric Badger created YARN-4756: - Summary: Unnecessary wait in Node Status Updater during reboot Key: YARN-4756 URL: https://issues.apache.org/jira/browse/YARN-4756 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.001.patch The optimization to notify the Node Status Updater thread to stop

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Description: The startStatusUpdater thread waits for the isStopped variable to be set to true, but it is

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15178409#comment-15178409 ] Eric Badger commented on YARN-4686: --- JIRA [YARN-4756] has been opened regarding the heartbeatMonitor

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.002.patch Fixing patch so that it applies to trunk instead of being dependent on

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15178599#comment-15178599 ] Eric Badger commented on YARN-4686: --- As per above comment, these test failures are not related to the

[jira] [Updated] (YARN-4760) proxy redirect to history server uses wrong URL

[ https://issues.apache.org/jira/browse/YARN-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4760: -- Attachment: YARN-4760.001.patch Simple patch. Just switching "apps" to "app" in the WebAppProxyServlet

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.004.patch Fixing whitespace in patch. > Unnecessary wait in Node Status Updater

[jira] [Commented] (YARN-4556) TestFifoScheduler.testResourceOverCommit fails

[ https://issues.apache.org/jira/browse/YARN-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258379#comment-15258379 ] Eric Badger commented on YARN-4556: --- Thanks, [~eepayne]! > TestFifoScheduler.testResourceOverCommit

[jira] [Updated] (YARN-4556) TestFifoScheduler.testResourceOverCommit fails

[ https://issues.apache.org/jira/browse/YARN-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4556: -- Attachment: YARN-4556-branch-2.7.001.patch > TestFifoScheduler.testResourceOverCommit fails >

[jira] [Reopened] (YARN-4556) TestFifoScheduler.testResourceOverCommit fails

[ https://issues.apache.org/jira/browse/YARN-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reopened YARN-4556: --- Adding a 2.7 patch. > TestFifoScheduler.testResourceOverCommit fails >

[jira] [Commented] (YARN-4556) TestFifoScheduler.testResourceOverCommit fails

[ https://issues.apache.org/jira/browse/YARN-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254525#comment-15254525 ] Eric Badger commented on YARN-4556: --- [~eepayne], please review this patch and commit to branch-2.7 if you

[jira] [Updated] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5055: -- Attachment: YARN-5055.003.patch Attaching new patch that fixes test failure. > max per user can be

[jira] [Commented] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296380#comment-15296380 ] Eric Badger commented on YARN-5055: --- All of the test failures are irrelevant to this patch and are all

[jira] [Updated] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5055: -- Attachment: YARN-5055.001.patch Attaching patch that limits the max per user application limit to the

[jira] [Updated] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5055: -- Attachment: YARN-5055.004.patch Fixing checkstyle. > max per user can be larger than max per queue >

[jira] [Updated] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5055: -- Attachment: YARN-5055.005.patch Fixing the indent ran the code over 80 characters. Now fixing that

[jira] [Updated] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5055: -- Attachment: YARN-5055.002.patch Fixing checkstyle. > max per user can be larger than max per queue >

[jira] [Updated] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5053: -- Attachment: YARN-5053.002.patch Attaching patch that builds string based on whether getRemoteAddress()

[jira] [Updated] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5053: -- Attachment: YARN-5053.004.patch Fixing checkstyle issue. > More informative diagnostics when

[jira] [Updated] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5053: -- Attachment: YARN-5053.003.patch I forgot that strings in Java are immutable. Updating the patch to fix

[jira] [Commented] (YARN-5069) TestFifoScheduler.testResourceOverCommit race condition

[ https://issues.apache.org/jira/browse/YARN-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280334#comment-15280334 ] Eric Badger commented on YARN-5069: --- [~eepayne], you committed [YARN-4556], which is similar to this. Can

[jira] [Updated] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5053: -- Attachment: YARN-5053.005.patch [~templedf], the last few patches have been small fixes. One was a

[jira] [Commented] (YARN-5069) TestFifoScheduler.testResourceOverCommit race condition

[ https://issues.apache.org/jira/browse/YARN-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15285255#comment-15285255 ] Eric Badger commented on YARN-5069: --- Thanks, [~eepayne]! > TestFifoScheduler.testResourceOverCommit race

[jira] [Commented] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280724#comment-15280724 ] Eric Badger commented on YARN-5053: --- [~sunilg], my attempt is to print out the address from where the

[jira] [Assigned] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned YARN-5053: - Assignee: Eric Badger > More informative diagnostics when applications killed by a user >

[jira] [Assigned] (YARN-5055) max per user can be larger than max per queue

[ https://issues.apache.org/jira/browse/YARN-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned YARN-5055: - Assignee: Eric Badger > max per user can be larger than max per queue >

[jira] [Created] (YARN-5069) TestFifoScheduler.testResourceOverCommit race condition

Eric Badger created YARN-5069: - Summary: TestFifoScheduler.testResourceOverCommit race condition Key: YARN-5069 URL: https://issues.apache.org/jira/browse/YARN-5069 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-5069) TestFifoScheduler.testResourceOverCommit race condition

[ https://issues.apache.org/jira/browse/YARN-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5069: -- Attachment: YARN-5069.001.patch Attaching trunk patch. > TestFifoScheduler.testResourceOverCommit race

[jira] [Updated] (YARN-5069) TestFifoScheduler.testResourceOverCommit race condition

[ https://issues.apache.org/jira/browse/YARN-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5069: -- Attachment: YARN-5069-b2.7.001.patch Attaching branch 2.7 patch. >

[jira] [Commented] (YARN-4747) AHS error 500 due to NPE when container start event is missing

[ https://issues.apache.org/jira/browse/YARN-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248641#comment-15248641 ] Eric Badger commented on YARN-4747: --- There's no immediate rush to get this in. I was just making sure

[jira] [Commented] (YARN-4747) AHS error 500 due to NPE when container start event is missing

[ https://issues.apache.org/jira/browse/YARN-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246546#comment-15246546 ] Eric Badger commented on YARN-4747: --- [~varun_saxena], are you still working on this? If not, I can take

[jira] [Updated] (YARN-5053) More informative diagnostics when applications killed by a user

[ https://issues.apache.org/jira/browse/YARN-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5053: -- Attachment: YARN-5053.001.patch Attaching patch. > More informative diagnostics when applications

[jira] [Commented] (YARN-1468) TestRMRestart.testRMRestartWaitForPreviousAMToFinish get failed.

[ https://issues.apache.org/jira/browse/YARN-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396233#comment-15396233 ] Eric Badger commented on YARN-1468: --- [~djp], you are correct. When I encountered the error in a test

[jira] [Comment Edited] (YARN-1468) TestRMRestart.testRMRestartWaitForPreviousAMToFinish get failed.

[ https://issues.apache.org/jira/browse/YARN-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396233#comment-15396233 ] Eric Badger edited comment on YARN-1468 at 7/27/16 7:51 PM: [~djp], you are

[jira] [Commented] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped

[ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396285#comment-15396285 ] Eric Badger commented on YARN-5416: --- Thanks for the response, Jason. That's exactly what I was thinking.

[jira] [Comment Edited] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped

[ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396285#comment-15396285 ] Eric Badger edited comment on YARN-5416 at 7/27/16 8:30 PM: Thanks for the

[jira] [Commented] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped

[ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388301#comment-15388301 ] Eric Badger commented on YARN-5416: --- [~djp], is there any reason why we would only add the

[jira] [Updated] (YARN-5462) TestNodeStatusUpdater.testNodeStatusUpdaterRetryAndNMShutdown fails intermittently

[ https://issues.apache.org/jira/browse/YARN-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5462: -- Attachment: YARN-5462.001.patch Attaching patch that adds an extra barrier to the serviceStop method for

[jira] [Created] (YARN-5462) TestNodeStatusUpdater.testNodeStatusUpdaterRetryAndNMShutdown fails intermittently

Eric Badger created YARN-5462: - Summary: TestNodeStatusUpdater.testNodeStatusUpdaterRetryAndNMShutdown fails intermittently Key: YARN-5462 URL: https://issues.apache.org/jira/browse/YARN-5462 Project:

[jira] [Updated] (YARN-5463) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

[ https://issues.apache.org/jira/browse/YARN-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5463: -- Attachment: YARN-5463.001.patch Attaching patch to catch and ignore IllegalArgumentExceptions along with

[jira] [Commented] (YARN-5463) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

[ https://issues.apache.org/jira/browse/YARN-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404293#comment-15404293 ] Eric Badger commented on YARN-5463: --- YARN-3602 fixed IOException, we need to now add

[jira] [Created] (YARN-5463) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

Eric Badger created YARN-5463: - Summary: TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup Key: YARN-5463 URL:

[jira] [Resolved] (YARN-5463) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

[ https://issues.apache.org/jira/browse/YARN-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger resolved YARN-5463. --- Resolution: Duplicate Closing as a dup of YARN-4717. Not sure how I didn't see the old one before I

[jira] [Commented] (YARN-4717) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

[ https://issues.apache.org/jira/browse/YARN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404351#comment-15404351 ] Eric Badger commented on YARN-4717: --- [~templedf], [~rkanter], can we cherry-pick this back to 2.7? I just

[jira] [Commented] (YARN-4974) Random test failure:TestRMApplicationHistoryWriter#testRMWritingMassiveHistoryForCapacitySche

[ https://issues.apache.org/jira/browse/YARN-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414291#comment-15414291 ] Eric Badger commented on YARN-4974: --- I think that the problem here is that this test assumes that there

[jira] [Assigned] (YARN-5469) Increase timeout of TestAmFilter.testFilter

[ https://issues.apache.org/jira/browse/YARN-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned YARN-5469: - Assignee: Eric Badger > Increase timeout of TestAmFilter.testFilter >

[jira] [Updated] (YARN-5469) Increase timeout of TestAmFilter.testFilter

[ https://issues.apache.org/jira/browse/YARN-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5469: -- Attachment: YARN-5469.001.patch Attaching patch to increase timeout to 10 seconds. > Increase timeout

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.010.patch Somehow change didn't get into last patch. Double checked that it's in

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.010-b2.patch Apologies for the bad Java 7 patch! I'll be sure to compile against

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641-branch-2.011.patch Changed isAlive() method to private > Localizer leaves behind

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843050#comment-15843050 ] Eric Badger commented on YARN-5641: --- Thanks, [~jlowe]! > Localizer leaves behind tarballs after

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840535#comment-15840535 ] Eric Badger commented on YARN-5641: --- The test failures are unrelated. However, since I got rid of the

[jira] [Commented] (YARN-4954) TestYarnClient.testReservationAPIs fails on machines with less than 4 GB available memory

[ https://issues.apache.org/jira/browse/YARN-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881074#comment-15881074 ] Eric Badger commented on YARN-4954: --- [~leftnoteasy], YARN-5389 fixed the timeout failures related to the

[jira] [Comment Edited] (YARN-4954) TestYarnClient.testReservationAPIs fails on machines with less than 4 GB available memory

[ https://issues.apache.org/jira/browse/YARN-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881074#comment-15881074 ] Eric Badger edited comment on YARN-4954 at 2/23/17 7:29 PM: [~leftnoteasy],

[jira] [Resolved] (YARN-5700) testAMRestartNotLostContainerCompleteMsg times out intermittently in 2.8

[ https://issues.apache.org/jira/browse/YARN-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger resolved YARN-5700. --- Resolution: Cannot Reproduce Revisited this and I cannot reproduce the failure. Closing as cannot

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.007.patch Previous patch did some things that JUnit didn't like. This patch fixes

[jira] [Updated] (YARN-5994) TestCapacityScheduler.testAMLimitUsage fails intermittently

[ https://issues.apache.org/jira/browse/YARN-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5994: -- Attachment: YARN-5994.001.patch Turns out the problem was on the scheduler side. {{rm.submitApp()}} was

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.008.patch Thanks for the review, [~jlowe]! I agree with all of your comments and

[jira] [Commented] (YARN-5994) TestCapacityScheduler.testAMLimitUsage fails intermittently

[ https://issues.apache.org/jira/browse/YARN-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831927#comment-15831927 ] Eric Badger commented on YARN-5994: --- [~bibinchundatt], [~sunilg], could you please review the latest

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.009.patch bq. It should be either java.util.concurrent.ConcurrentHashMap (and

[jira] [Created] (YARN-5622) TestYarnCLI.testGetContainers fails due to mismatched date formats

Eric Badger created YARN-5622: - Summary: TestYarnCLI.testGetContainers fails due to mismatched date formats Key: YARN-5622 URL: https://issues.apache.org/jira/browse/YARN-5622 Project: Hadoop YARN

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487505#comment-15487505 ] Eric Badger commented on YARN-5641: --- [~Naganarasimha], I see the issue in 2.7. I suspect that it is also

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487533#comment-15487533 ] Eric Badger commented on YARN-5641: --- The problem appears to be a race between FileUtil.java:unTarUsingTar

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487350#comment-15487350 ] Eric Badger commented on YARN-5641: --- Here is an example log of the failure. The localizer attempts to

[jira] [Commented] (YARN-1468) TestRMRestart.testRMRestartWaitForPreviousAMToFinish get failed.

[ https://issues.apache.org/jira/browse/YARN-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487300#comment-15487300 ] Eric Badger commented on YARN-1468: --- [~templedf], there's some additional analysis for this failure in

[jira] [Created] (YARN-5641) Localizer leaves behind tarballs after container is complete

Eric Badger created YARN-5641: - Summary: Localizer leaves behind tarballs after container is complete Key: YARN-5641 URL: https://issues.apache.org/jira/browse/YARN-5641 Project: Hadoop YARN

[jira] [Commented] (YARN-5700) testAMRestartNotLostContainerCompleteMsg times out intermittently in 2.8

[ https://issues.apache.org/jira/browse/YARN-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546852#comment-15546852 ] Eric Badger commented on YARN-5700: --- Looks like there are 2 bugs here. 1) TestAMRestart uses

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503590#comment-15503590 ] Eric Badger commented on YARN-5641: --- TestDNS and TestWebDelegationToken don't fail for me locally and are

[jira] [Commented] (YARN-5491) Random Failure TestCapacityScheduler#testCSQueueBlocked

[ https://issues.apache.org/jira/browse/YARN-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503937#comment-15503937 ] Eric Badger commented on YARN-5491: --- [~varun_saxena], I am seeing this same failure on branch-2.8. Can

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.003.patch Attaching new patch that adds in a unit test to make sure that the

[jira] [Commented] (YARN-5622) TestYarnCLI.testGetContainers fails due to mismatched date formats

[ https://issues.apache.org/jira/browse/YARN-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516793#comment-15516793 ] Eric Badger commented on YARN-5622: --- [~ajisakaa], it doesn't currently fail in trunk because the

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506564#comment-15506564 ] Eric Badger commented on YARN-5641: --- The test failure is unrelated to this patch and passes for me

[jira] [Commented] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496398#comment-15496398 ] Eric Badger commented on YARN-5641: --- [~jlowe] and I worked on this for some time yesterday and killing

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.001.patch Attaching a patch that creates a separate thread to read the input

[jira] [Updated] (YARN-5641) Localizer leaves behind tarballs after container is complete

[ https://issues.apache.org/jira/browse/YARN-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-5641: -- Attachment: YARN-5641.002.patch This new patch should fix most, if not all, of the test failures. The

  1   2   3   4   5   6   7   8   9   10   >