[jira] [Created] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

yeshavora created YARN-1057: --- Summary: Add mechanism to check validity of a Node to be Added/Excluded Key: YARN-1057 URL: https://issues.apache.org/jira/browse/YARN-1057 Project: Hadoop YARN

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-353: -- Attachment: YARN-353.13.patch Add Zookeeper-based store implementation for RMStateStore

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-353: -- Attachment: (was: YARN-353.13.patch) Add Zookeeper-based store implementation for

[jira] [Updated] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-353: -- Attachment: (was: YARN-353.13.patch) Add Zookeeper-based store implementation for

[jira] [Updated] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1057: -- Issue Type: Improvement (was: Bug) Add mechanism to check validity of a

[jira] [Created] (YARN-1058) Recovery issues on RM Restart with FileSystemRMStateStore

Karthik Kambatla created YARN-1058: -- Summary: Recovery issues on RM Restart with FileSystemRMStateStore Key: YARN-1058 URL: https://issues.apache.org/jira/browse/YARN-1058 Project: Hadoop YARN

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736688#comment-13736688 ] Karthik Kambatla commented on YARN-353: --- Tested the latest patch on pseudo-dist

[jira] [Assigned] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-353: - Assignee: Karthik Kambatla (was: Bikas Saha) Add Zookeeper-based store

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736695#comment-13736695 ] Karthik Kambatla commented on YARN-353: --- Assigned to myself for easier tracking. The

[jira] [Updated] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rvller updated YARN-1059: - Component/s: resourcemanager Affects Version/s: 2.0.5-alpha IllegalArgumentException while

[jira] [Updated] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rvller updated YARN-1059: - Description: Here is the traceback while starting the yarn resourse manager: 2013-08-12 12:53:29,319 FATAL

[jira] [Updated] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-291: Attachment: YARN-291-CoreAndAdmin.patch Update patch against latest trunk with core changes and admin

[jira] [Commented] (YARN-291) Dynamic resource configuration

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

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736894#comment-13736894 ] Robert Joseph Evans commented on YARN-624: -- From my perspective it does not really

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736919#comment-13736919 ] Robert Joseph Evans commented on YARN-1024: --- Perhaps I am missing something here.

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736970#comment-13736970 ] Carlo Curino commented on YARN-624: --- Robert, you are right, and provide a compelling

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736976#comment-13736976 ] Alejandro Abdelnur commented on YARN-1008: -- Omkar, I agree with you with not

[jira] [Commented] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737009#comment-13737009 ] Hitesh Shah commented on YARN-1057: --- [~yeshavora] Could you clarify what you mean by an

[jira] [Commented] (YARN-1058) Recovery issues on RM Restart with FileSystemRMStateStore

[ https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737021#comment-13737021 ] Bikas Saha commented on YARN-1058: -- The first one is expected because the RM is currently

[jira] [Commented] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737030#comment-13737030 ] yeshavora commented on YARN-1057: - By 'Invalide hostname/node', I mean the incorrect name

[jira] [Commented] (YARN-954) [YARN-321] History Service should create the webUI and wire it to HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737062#comment-13737062 ] Zhijie Shen commented on YARN-954: -- Thanks [~devaraj.k] for your work. I've some comments

[jira] [Commented] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737073#comment-13737073 ] Steve Loughran commented on YARN-1059: -- It looks the root cause is that you've got

[jira] [Commented] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737074#comment-13737074 ] Bikas Saha commented on YARN-1055: -- what is the scenario? if this means dont rerun a job

[jira] [Commented] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737076#comment-13737076 ] Vinod Kumar Vavilapalli commented on YARN-1055: --- Yeah, that sounds about

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-854: - Fix Version/s: 2.0.6-alpha App submission fails on secure deploy

[jira] [Commented] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737081#comment-13737081 ] Vinod Kumar Vavilapalli commented on YARN-854: -- Done.. App

[jira] [Commented] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737094#comment-13737094 ] Karthik Kambatla commented on YARN-1055: Thanks Bikas. I forgot about thtat -

[jira] [Resolved] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-1055. Resolution: Invalid App recovery should be configurable per application

[jira] [Assigned] (YARN-1058) Recovery issues on RM Restart with FileSystemRMStateStore

[ https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1058: -- Assignee: Karthik Kambatla Recovery issues on RM Restart with

[jira] [Commented] (YARN-1059) IllegalArgumentException while starting YARN

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737096#comment-13737096 ] rvller commented on YARN-1059: -- I've already thought about it. So I've tried to change it into

[jira] [Commented] (YARN-1058) Recovery issues on RM Restart with FileSystemRMStateStore

[ https://issues.apache.org/jira/browse/YARN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737100#comment-13737100 ] Jian He commented on YARN-1058: --- As Bikas said, the first exception is expected because

[jira] [Commented] (YARN-1023) [YARN-321] Weservices REST API's support for Application History

[ https://issues.apache.org/jira/browse/YARN-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737132#comment-13737132 ] Zhijie Shen commented on YARN-1023: --- For the second exception, is it better to say

[jira] [Updated] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1008: - Attachment: YARN-1008.patch new patch that undoes changes from PB and public API. The

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

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

[jira] [Commented] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737171#comment-13737171 ] Hitesh Shah commented on YARN-1057: --- Thanks for the clarification. I am not sure if it is

[jira] [Commented] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737200#comment-13737200 ] Vinod Kumar Vavilapalli commented on YARN-1055: --- Irrespective of RM restart,

[jira] [Commented] (YARN-987) Adding History Service to use Store and converting Historydata to Report

[ https://issues.apache.org/jira/browse/YARN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737215#comment-13737215 ] Zhijie Shen commented on YARN-987: -- It's not guranteed that the implementation of

[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=13737256#comment-13737256 ] Xuan Gong commented on YARN-107: bq.I thought the consensus was to not throw an exception in

[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=13737332#comment-13737332 ] Vinod Kumar Vavilapalli commented on YARN-107: -- Makes sense. The other point is

[jira] [Commented] (YARN-1055) App recovery should be configurable per application

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737487#comment-13737487 ] Karthik Kambatla commented on YARN-1055: Let me explain what I am getting at with

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737497#comment-13737497 ] Sangjin Lee commented on YARN-451: -- I think some information about the app size can be

[jira] [Updated] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1055: --- Summary: Handle app recovery differently for AM failures and RM restart (was: App recovery

[jira] [Updated] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1055: --- Description: Ideally, we would like to tolerate container, AM, RM failures. App recovery for

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737518#comment-13737518 ] Sangjin Lee commented on YARN-451: -- For sorting, it would be good to expose a number. How

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737641#comment-13737641 ] Vinod Kumar Vavilapalli commented on YARN-451: -- In YARN, resource usage by

[jira] [Commented] (YARN-1055) Handle app recovery differently for AM failures and RM restart

[ https://issues.apache.org/jira/browse/YARN-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737651#comment-13737651 ] Vinod Kumar Vavilapalli commented on YARN-1055: --- Irrespective of RM restart,

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

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

[jira] [Commented] (YARN-895) If NameNode is in safemode when RM restarts, RM should wait instead of crashing.

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

[jira] [Updated] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-643: --- Attachment: YARN-643.4.patch Address all latest comments WHY appToken is removed both in

[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=13737741#comment-13737741 ] Xuan Gong commented on YARN-107: bq.The other point is you should have a separate test to

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

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

[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.5.patch Address all latest comments

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737752#comment-13737752 ] Xuan Gong commented on YARN-643: bq.[WARNING]

[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=13737762#comment-13737762 ] Hadoop QA commented on YARN-107: {color:red}-1 overall{color}. Here are the results of

[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=13737767#comment-13737767 ] Xuan Gong commented on YARN-107: There javadoc warnings are not related to this patch.

[jira] [Commented] (YARN-895) If NameNode is in safemode when RM restarts, RM should wait instead of crashing.

[ https://issues.apache.org/jira/browse/YARN-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737804#comment-13737804 ] Jian He commented on YARN-895: -- Looks like 'SafeModeException' cannot be referenced from RM

[jira] [Updated] (YARN-895) If NameNode is in safemode when RM restarts, RM should wait instead of crashing.

[ https://issues.apache.org/jira/browse/YARN-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-895: - Attachment: YARN-895.1.patch If NameNode is in safemode when RM restarts, RM should wait instead of

[jira] [Commented] (YARN-895) If NameNode is in safemode when RM restarts, RM should wait instead of crashing.

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