[jira] [Resolved] (YARN-636) Restore clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-636. -- Resolution: Duplicate Eventually, this was done as part of YARN-582. Closing as

[jira] [Updated] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-582: - Summary: Restore appToken and clientToken for app attempt after RM restart (was: Restore appToken for app attempt

[jira] [Commented] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651666#comment-13651666 ] Hudson commented on YARN-582: - Integrated in Hadoop-trunk-Commit #3717 (See

[jira] [Commented] (YARN-651) Change ContainerManagerPBClientImpl and RMAdminProtocolPBClientImpl to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651779#comment-13651779 ] Hudson commented on YARN-651: - Integrated in Hadoop-Yarn-trunk #203 (See

[jira] [Commented] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651782#comment-13651782 ] Hudson commented on YARN-582: - Integrated in Hadoop-Yarn-trunk #203 (See

[jira] [Commented] (YARN-651) Change ContainerManagerPBClientImpl and RMAdminProtocolPBClientImpl to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651862#comment-13651862 ] Hudson commented on YARN-651: - Integrated in Hadoop-Hdfs-trunk #1392 (See

[jira] [Commented] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651865#comment-13651865 ] Hudson commented on YARN-582: - Integrated in Hadoop-Hdfs-trunk #1392 (See

[jira] [Commented] (YARN-651) Change ContainerManagerPBClientImpl and RMAdminProtocolPBClientImpl to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651911#comment-13651911 ] Hudson commented on YARN-651: - Integrated in Hadoop-Mapreduce-trunk #1419 (See

[jira] [Commented] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651914#comment-13651914 ] Hudson commented on YARN-582: - Integrated in Hadoop-Mapreduce-trunk #1419 (See

[jira] [Commented] (YARN-656) In scheduler UI, Memory Total should not include reserved memory.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651981#comment-13651981 ] Carlo Curino commented on YARN-656: --- Sandy, I am not sure about this one. I would expect

[jira] [Updated] (YARN-646) Some issues in Fair Scheduler's document

[ https://issues.apache.org/jira/browse/YARN-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated YARN-646: Target Version/s: 2.0.5-beta Some issues in Fair Scheduler's document

[jira] [Resolved] (YARN-646) Some issues in Fair Scheduler's document

[ https://issues.apache.org/jira/browse/YARN-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur resolved YARN-646. - Resolution: Fixed Hadoop Flags: Reviewed Some issues in Fair Scheduler's

[jira] [Commented] (YARN-646) Some issues in Fair Scheduler's document

[ https://issues.apache.org/jira/browse/YARN-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652082#comment-13652082 ] Hudson commented on YARN-646: - Integrated in Hadoop-trunk-Commit #3718 (See

[jira] [Commented] (YARN-656) In scheduler UI, Memory Total should not include reserved memory.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652107#comment-13652107 ] Sandy Ryza commented on YARN-656: - Agreed that memory total should be the total amount of

[jira] [Updated] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

[ https://issues.apache.org/jira/browse/YARN-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-655: Attachment: YARN-655.patch Fair scheduler metrics should subtract allocated memory from available

[jira] [Commented] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

[ https://issues.apache.org/jira/browse/YARN-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652186#comment-13652186 ] Sandy Ryza commented on YARN-655: - Uploaded patch that subtracts allocated memory from

[jira] [Commented] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

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

[jira] [Updated] (YARN-631) Change ClientRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-631: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Change

[jira] [Updated] (YARN-631) Change ClientRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-631: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Change

[jira] [Assigned] (YARN-634) Introduce a SerializedException

[ https://issues.apache.org/jira/browse/YARN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth reassigned YARN-634: --- Assignee: Siddharth Seth Introduce a SerializedException ---

[jira] [Updated] (YARN-634) Introduce a SerializedException

[ https://issues.apache.org/jira/browse/YARN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-634: Attachment: YARN-634.txt Patch pulls in changes from an older patch on MR-4067. Changes -

[jira] [Commented] (YARN-656) In scheduler UI, Memory Total should not include reserved memory.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652360#comment-13652360 ] Carlo Curino commented on YARN-656: --- I haven't seen this problem happening with the

[jira] [Commented] (YARN-634) Introduce a SerializedException

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

[jira] [Commented] (YARN-631) Change ClientRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652390#comment-13652390 ] Vinod Kumar Vavilapalli commented on YARN-631: -- Looks good, +1. Can you apply

[jira] [Commented] (YARN-631) Change ClientRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652415#comment-13652415 ] Xuan Gong commented on YARN-631: All YARN tests are passing on branch-2

[jira] [Created] (YARN-658) Command to kill a YARN application does not work with newer Ubuntu versions

David Yan created YARN-658: -- Summary: Command to kill a YARN application does not work with newer Ubuntu versions Key: YARN-658 URL: https://issues.apache.org/jira/browse/YARN-658 Project: Hadoop YARN

[jira] [Commented] (YARN-631) Change ClientRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652487#comment-13652487 ] Hudson commented on YARN-631: - Integrated in Hadoop-trunk-Commit #3723 (See

[jira] [Updated] (YARN-634) Introduce a SerializedException

[ https://issues.apache.org/jira/browse/YARN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-634: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Introduce a

[jira] [Commented] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652515#comment-13652515 ] Karthik Kambatla commented on YARN-568: --- In {{Allocation}}, the two fields fungible*

[jira] [Updated] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-630: --- Attachment: YARN-630.1.patch Change AMRMProtocol api to throw IOException and YarnRemoteException

[jira] [Commented] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652525#comment-13652525 ] Xuan Gong commented on YARN-630: The MR changes are in MAPREDUCE-5226

[jira] [Commented] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652526#comment-13652526 ] Xuan Gong commented on YARN-630: Test cases are passing on branch-2 and trunk

[jira] [Commented] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652548#comment-13652548 ] Carlo Curino commented on YARN-568: --- [~kkambatl] This code was originally in YARN-567

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652557#comment-13652557 ] Alejandro Abdelnur commented on YARN-392: - [~bikassaha], are you OK going with a

[jira] [Commented] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

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

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Attachment: YARN-569.1.patch CapacityScheduler: support for preemption (using a capacity monitor)

[jira] [Commented] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652598#comment-13652598 ] Carlo Curino commented on YARN-568: --- Updated [patch for YARN-569 |

[jira] [Created] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

Vinod Kumar Vavilapalli created YARN-659: Summary: RMStateStore's removeApplication APIs should just take an applicationId Key: YARN-659 URL: https://issues.apache.org/jira/browse/YARN-659

[jira] [Updated] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-617: --- Attachment: YARN-617.20130508.patch In unsercure mode, AM can fake resource requirements

[jira] [Commented] (YARN-634) Introduce a SerializedException

[ https://issues.apache.org/jira/browse/YARN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652617#comment-13652617 ] Siddharth Seth commented on YARN-634: - bq. Move SerializedException to be in server-api

[jira] [Commented] (YARN-617) In unsercure mode, AM can fake resource requirements

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

[jira] [Commented] (YARN-638) Restore RMDelegationTokens after RM Restart

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

[jira] [Updated] (YARN-638) Restore RMDelegationTokens after RM Restart

[ https://issues.apache.org/jira/browse/YARN-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-638: - Attachment: YARN-638.5.patch fixed test failure Restore RMDelegationTokens after RM Restart

[jira] [Commented] (YARN-638) Restore RMDelegationTokens after RM Restart

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

[jira] [Commented] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652746#comment-13652746 ] Vinod Kumar Vavilapalli commented on YARN-630: -- +1, this looks good. Checking

[jira] [Updated] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-630: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Change

[jira] [Updated] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-630: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Change AMRMProtocol

[jira] [Updated] (YARN-629) Make YarnRemoteException not be rooted at IOException

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-629: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Make

[jira] [Updated] (YARN-629) Make YarnRemoteException not be rooted at IOException

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-629: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Make

[jira] [Updated] (YARN-632) Change ContainerManager api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-632: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Change

[jira] [Updated] (YARN-633) Change RMAdminProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-633: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Change

[jira] [Updated] (YARN-633) Change RMAdminProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-633: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Change

[jira] [Updated] (YARN-625) Move unwrapAndThrowException from YarnRemoteExceptionPBImpl to RPCUtil

[ https://issues.apache.org/jira/browse/YARN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-625: - Issue Type: Sub-task (was: Task) Parent: YARN-142 Move

[jira] [Commented] (YARN-630) Change AMRMProtocol api to throw IOException and YarnRemoteException

[ https://issues.apache.org/jira/browse/YARN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652763#comment-13652763 ] Hudson commented on YARN-630: - Integrated in Hadoop-trunk-Commit #3724 (See

[jira] [Updated] (YARN-635) Rename YarnRemoteException to YarnException

[ https://issues.apache.org/jira/browse/YARN-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-635: - Issue Type: Sub-task (was: Bug) Parent: YARN-142 Rename

[jira] [Updated] (YARN-635) Rename YarnRemoteException to YarnException

[ https://issues.apache.org/jira/browse/YARN-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-635: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Rename

[jira] [Updated] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-613: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-386) Create

[jira] [Updated] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-613: - Issue Type: Sub-task (was: Bug) Parent: YARN-47 Create NM proxy per