[jira] [Updated] (YARN-875) Application can hang if AMRMClientAsync callback thread has exception

[ https://issues.apache.org/jira/browse/YARN-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-875: --- Attachment: YARN-875.4.patch Application can hang if AMRMClientAsync callback thread has exception

[jira] [Updated] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

[ https://issues.apache.org/jira/browse/YARN-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-906: - Summary: Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed (was:

[jira] [Commented] (YARN-245) Node Manager can not handle duplicate responses

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

[jira] [Updated] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-966: - Attachment: YARN-966.1.patch Created a patch: 1. ContainerImpl#getLocalizedResources returns null when

[jira] [Updated] (YARN-502) RM crash with NPE on NODE_REMOVED event with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-502: --- Attachment: YARN-502-trunk-3.patch Attaching patch Thanks, Mayank RM crash with NPE

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-875) Application can hang if AMRMClientAsync callback thread has exception

[ https://issues.apache.org/jira/browse/YARN-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718141#comment-13718141 ] Hadoop QA commented on YARN-875: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718142#comment-13718142 ] Hadoop QA commented on YARN-903: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-245) Node Manager can not handle duplicate responses

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

[jira] [Commented] (YARN-961) ContainerManagerImpl should enforce token on server. Today it is [TOKEN, SIMPLE]

[ https://issues.apache.org/jira/browse/YARN-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718159#comment-13718159 ] Hadoop QA commented on YARN-961: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event with FairScheduler

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

[jira] [Created] (YARN-967) Command Line Interface(CLI) for Reading Application History Storage Data

Devaraj K created YARN-967: -- Summary: Command Line Interface(CLI) for Reading Application History Storage Data Key: YARN-967 URL: https://issues.apache.org/jira/browse/YARN-967 Project: Hadoop YARN

[jira] [Commented] (YARN-964) Give a parameter that can set AM retry interval

[ https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718338#comment-13718338 ] Thomas Graves commented on YARN-964: How many NM's did you have? How would an AM retry

[jira] [Updated] (YARN-949) Failed log aggregation can leave a file open.

[ https://issues.apache.org/jira/browse/YARN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-949: Target Version/s: 0.23.10 Affects Version/s: (was: 2.1.0-beta) Sounds good to me. Adjusting

[jira] [Commented] (YARN-961) ContainerManagerImpl should enforce token on server. Today it is [TOKEN, SIMPLE]

[ https://issues.apache.org/jira/browse/YARN-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718460#comment-13718460 ] Omkar Vinit Joshi commented on YARN-961: [~daryn] I see there is some difference

[jira] [Commented] (YARN-701) ApplicationTokens should be used irrespective of kerberos

[ https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718465#comment-13718465 ] Alejandro Abdelnur commented on YARN-701: - we should solve this in the same way HDFS

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718504#comment-13718504 ] Omkar Vinit Joshi commented on YARN-389: [~zjshen] [~bikassaha] I think we should

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718568#comment-13718568 ] Alejandro Abdelnur commented on YARN-389: - Wouldn't make sense to add a new status

[jira] [Commented] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718623#comment-13718623 ] Kihwal Lee commented on YARN-968: - The protocol was renamed in YARN-387.

[jira] [Resolved] (YARN-195) AM should have a way of telling RM to not allocate containers on some nodes

[ https://issues.apache.org/jira/browse/YARN-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha resolved YARN-195. - Resolution: Fixed The blacklist API on the scheduler fixes this. AM should have a way of

[jira] [Resolved] (YARN-564) Job history logs do not log anything when JVM fails to start

[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-564. -- Resolution: Fixed Assignee: Jian He Job history logs do not log anything when JVM fails to start

[jira] [Commented] (YARN-564) Job history logs do not log anything when JVM fails to start

[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718642#comment-13718642 ] Jian He commented on YARN-564: -- This was fixed along with YARN-814 reproduced as mentioned

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718653#comment-13718653 ] Omkar Vinit Joshi commented on YARN-389: Today this limit is static. This by default

[jira] [Assigned] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-968: Assignee: Vinod Kumar Vavilapalli RM admin commands don't work

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718661#comment-13718661 ] German Florez-Larrahondo commented on YARN-926: --- Team, I'm getting errors

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718666#comment-13718666 ] Bikas Saha commented on YARN-389: - I dont think we can be good at predicting the future and

[jira] [Commented] (YARN-389) Infinitely assigning containers when the required resource exceeds the cluster's absolute capacity

[ https://issues.apache.org/jira/browse/YARN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718673#comment-13718673 ] Hitesh Shah commented on YARN-389: -- The static limit is there for a reason. No application

[jira] [Updated] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-937: Attachment: YARN-937.patch Updated patch fixing typos and making sure the jobtoken file

[jira] [Commented] (YARN-56) Handle container requests that request more resources than currently available in the cluster

[ https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718675#comment-13718675 ] Omkar Vinit Joshi commented on YARN-56: --- I agree timeout behavior will be useful but we

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718694#comment-13718694 ] Vinod Kumar Vavilapalli commented on YARN-926: -- I just built it again, it

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718698#comment-13718698 ] Jian He commented on YARN-926: -- I also tried, it should work. can you do mvn clean

[jira] [Updated] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

[ https://issues.apache.org/jira/browse/YARN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-932: -- Attachment: yarn-932-1.patch The fix is trivial - set the log_dir in testLocalizationInit

[jira] [Commented] (YARN-926) ContainerManagerProtcol APIs should take in requests for multiple containers

[ https://issues.apache.org/jira/browse/YARN-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718710#comment-13718710 ] German Florez-Larrahondo commented on YARN-926: --- Team, you are right, a 'mvn

[jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718713#comment-13718713 ] Bikas Saha commented on YARN-937: - bq. We need to get the scheduler HOST:PORT to set the

[jira] [Updated] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-968: - Attachment: YARN-968.txt It's broken on trunk too, but only when

[jira] [Commented] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

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

[jira] [Created] (YARN-969) Fair Scheduler should validate the release container list before actually releasing them

Sandy Ryza created YARN-969: --- Summary: Fair Scheduler should validate the release container list before actually releasing them Key: YARN-969 URL: https://issues.apache.org/jira/browse/YARN-969 Project:

[jira] [Commented] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

[ https://issues.apache.org/jira/browse/YARN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718729#comment-13718729 ] Sandy Ryza commented on YARN-932: - Thanks Karthik. +1

[jira] [Commented] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718736#comment-13718736 ] Hadoop QA commented on YARN-968: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718750#comment-13718750 ] Kihwal Lee commented on YARN-968: - +1 The patch looks good. Are you going to file a jira for

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718753#comment-13718753 ] Omkar Vinit Joshi commented on YARN-957: No this is completely different as RM here

[jira] [Assigned] (YARN-948) CapacityScheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-948: -- Assignee: Omkar Vinit Joshi CapacityScheduler should validate the release container

[jira] [Updated] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

[ https://issues.apache.org/jira/browse/YARN-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-688: - Attachment: YARN-688.4.patch updated patch Containers not cleaned up when NM received SHUTDOWN

[jira] [Commented] (YARN-948) CapacityScheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718768#comment-13718768 ] Bikas Saha commented on YARN-948: - If this is a check that a container matches the

[jira] [Commented] (YARN-948) CapacityScheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718770#comment-13718770 ] Hitesh Shah commented on YARN-948: -- +1 to [~tucu00]'s comment on this check being done in

[jira] [Commented] (YARN-948) CapacityScheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718767#comment-13718767 ] Omkar Vinit Joshi commented on YARN-948: [~tucu00] yes makes sense.. adding an

[jira] [Updated] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-948: Summary: RM should validate the release container list before actually releasing them (was:

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718782#comment-13718782 ] Bikas Saha commented on YARN-948: - Changing title to reflect that this is not scheduler

[jira] [Commented] (YARN-155) TestAppManager intermittently fails with jdk7

[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718783#comment-13718783 ] Karthik Kambatla commented on YARN-155: --- YARN-599 fixes this in branch-2.

[jira] [Updated] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-948: Description: At present we are blinding passing the allocate request containing containers to be released

[jira] [Resolved] (YARN-969) Fair Scheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-969. Resolution: Duplicate Fair Scheduler should validate the release container list before

[jira] [Assigned] (YARN-969) Fair Scheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-969: -- Assignee: Omkar Vinit Joshi Fair Scheduler should validate the release container

[jira] [Commented] (YARN-969) Fair Scheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718784#comment-13718784 ] Omkar Vinit Joshi commented on YARN-969: [~sandyr] I think a fix in

[jira] [Commented] (YARN-155) TestAppManager intermittently fails with jdk7

[ https://issues.apache.org/jira/browse/YARN-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718787#comment-13718787 ] Karthik Kambatla commented on YARN-155: --- By the way, +1 to the patch for branch-0.23.

[jira] [Updated] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

[ https://issues.apache.org/jira/browse/YARN-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-906: - Attachment: YARN-906.2.patch Updated the patch: 1. Removed the logic of cancelling scheduled

[jira] [Commented] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

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

[jira] [Commented] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

[ https://issues.apache.org/jira/browse/YARN-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718810#comment-13718810 ] Hadoop QA commented on YARN-906: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718819#comment-13718819 ] Bikas Saha commented on YARN-873: - Per Vinod's comment above we should make sure other API's

[jira] [Commented] (YARN-969) Fair Scheduler should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718823#comment-13718823 ] Sandy Ryza commented on YARN-969: - [~ojoshi], makes sense to me. Fair

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718831#comment-13718831 ] Xuan Gong commented on YARN-873: bq.Per Vinod's comment above we should make sure other

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718836#comment-13718836 ] Xuan Gong commented on YARN-873: We can fix them together

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718839#comment-13718839 ] Bikas Saha commented on YARN-873: - Its fine if its a different patch. Please make sure that

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718845#comment-13718845 ] Kihwal Lee commented on YARN-960: - The tasks are blowing up in the test: {noformat}

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718867#comment-13718867 ] Bikas Saha commented on YARN-873: - +1. Committing to trunk, branch-2 and branch-2.1-beta.

[jira] [Updated] (YARN-970) Add tests for RMAdmin

[ https://issues.apache.org/jira/browse/YARN-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-970: - Description: We don't have any tests as of now. In the minimum, we should write a

[jira] [Created] (YARN-970) Add tests for RMAdmin

Vinod Kumar Vavilapalli created YARN-970: Summary: Add tests for RMAdmin Key: YARN-970 URL: https://issues.apache.org/jira/browse/YARN-970 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-968) RM admin commands don't work

[ https://issues.apache.org/jira/browse/YARN-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1371#comment-1371 ] Vinod Kumar Vavilapalli commented on YARN-968: -- Are you going to file a jira

[jira] [Updated] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-948: --- Attachment: YARN-948-20130724.patch RM should validate the release container list before

[jira] [Created] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

Hitesh Shah created YARN-971: Summary: hadoop-yarn-api pom does not define a dependencies tag Key: YARN-971 URL: https://issues.apache.org/jira/browse/YARN-971 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-937: Attachment: YARN-937.patch Oops, sorry missed Vinod's comments before, uploading new patch

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

Project: Hadoop YARN Issue Type: Bug Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: YARN-948-20130724.patch At present we are blinding passing the allocate request containing containers to be released to the scheduler. This may

[jira] [Commented] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

[ https://issues.apache.org/jira/browse/YARN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718922#comment-13718922 ] Alejandro Abdelnur commented on YARN-932: - wouldn't be the right fix to find out

[jira] [Updated] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

[ https://issues.apache.org/jira/browse/YARN-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-688: - Attachment: YARN-688.5.patch Updated the test, the test will fail without NM changes and pass with changes.

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12594042/YARN-948-20130724.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2

[jira] [Created] (YARN-972) Allow requests and scheduling for fractional virtual cores

Sandy Ryza created YARN-972: --- Summary: Allow requests and scheduling for fractional virtual cores Key: YARN-972 URL: https://issues.apache.org/jira/browse/YARN-972 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

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

[jira] [Updated] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated YARN-960: - Attachment: YARN-960.patch All tokens but the AMRM token are being lost are lost if security is disabled.

[jira] [Commented] (YARN-945) AM register failing after AMRMToken

[ https://issues.apache.org/jira/browse/YARN-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718975#comment-13718975 ] Daryn Sharp commented on YARN-945: -- Please be sure I get a chance to look at the patch.

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719001#comment-13719001 ] Hadoop QA commented on YARN-960: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719003#comment-13719003 ] Bikas Saha commented on YARN-744: - Patch needs rebase. Probably reuse the recently added

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719006#comment-13719006 ] Omkar Vinit Joshi commented on YARN-957: thanks [~hitesh] for pointing this out..I

[jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719009#comment-13719009 ] Hadoop QA commented on YARN-937: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-910) Allow auxiliary services to listen for container starts and completions

[ https://issues.apache.org/jira/browse/YARN-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719020#comment-13719020 ] Karthik Kambatla commented on YARN-910: --- MAPREDUCE-5418 will require something like

[jira] [Updated] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

[ https://issues.apache.org/jira/browse/YARN-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-971: Attachment: yarn-971-v1.patch hadoop-yarn-api pom does not define a dependencies tag

[jira] [Commented] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

[ https://issues.apache.org/jira/browse/YARN-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719056#comment-13719056 ] Ted Yu commented on YARN-971: - Please take a look at patch v1. hadoop-yarn-api

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719066#comment-13719066 ] Alejandro Abdelnur commented on YARN-960: - LGTM. Still with this patch I cannot get

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719071#comment-13719071 ] Xuan Gong commented on YARN-107: In Yarn-873, we introduced ApplicationNotFoundException.

[jira] [Updated] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-107: --- Attachment: YARN-107.1.patch ClientRMService.forceKillApplication() should handle the non-RUNNING

[jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719089#comment-13719089 ] Alejandro Abdelnur commented on YARN-937: - test failures seem unrelated, those

[jira] [Updated] (YARN-934) Defining Writing Interface of HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-934: - Attachment: YARN-934.2.patch Updated the patch: 1. The abstract methods have the protobuf classes as the

[jira] [Commented] (YARN-934) Defining Writing Interface of HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719118#comment-13719118 ] Hadoop QA commented on YARN-934: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-961) ContainerManagerImpl should enforce token on server. Today it is [TOKEN, SIMPLE]

[ https://issues.apache.org/jira/browse/YARN-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-961: --- Attachment: YARN-961-20130724.1.patch ContainerManagerImpl should enforce token on

[jira] [Commented] (YARN-961) ContainerManagerImpl should enforce token on server. Today it is [TOKEN, SIMPLE]

[ https://issues.apache.org/jira/browse/YARN-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13719156#comment-13719156 ] Hadoop QA commented on YARN-961: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

[ https://issues.apache.org/jira/browse/YARN-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-688: - Attachment: YARN-688.6.patch Containers not cleaned up when NM received SHUTDOWN event from

[jira] [Commented] (YARN-688) Containers not cleaned up when NM received SHUTDOWN event from NodeStatusUpdater

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