[jira] [Commented] (YARN-1027) Implement RMHAServiceProtocol

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759973#comment-13759973 ] Bikas Saha commented on YARN-1027: -- The patch look clean overall. I would suggest

[jira] [Commented] (YARN-1059) '\n' or ' ' or '\t' should be ignored for some configuration parameters

[ https://issues.apache.org/jira/browse/YARN-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760042#comment-13760042 ] Tsuyoshi OZAWA commented on YARN-1059: -- Threw a patch to HADOOP-9869.

[jira] [Commented] (YARN-1132) QueueMetrics.java has wrong comments

[ https://issues.apache.org/jira/browse/YARN-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760045#comment-13760045 ] Tsuyoshi OZAWA commented on YARN-1132: -- Then, this should be closed as duplicated jira

[jira] [Updated] (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:all-tabpanel ] Alejandro Abdelnur updated YARN-910: Attachment: YARN-910.patch Thanks Sandy Vinod. In the latest patch I've took care of all

[jira] [Created] (YARN-1159) NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL

Alejandro Abdelnur created YARN-1159: Summary: NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL Key: YARN-1159 URL:

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

[jira] [Commented] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760128#comment-13760128 ] Steve Loughran commented on YARN-1155: -- This would need to work for clusters where DNS

[jira] [Moved] (YARN-1160) allow admins to force app deployment on a specific host

[ https://issues.apache.org/jira/browse/YARN-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran moved MAPREDUCE-4277 to YARN-1160: - Component/s: (was: mrv2)

[jira] [Commented] (YARN-1151) Ability to configure auxiliary services from HDFS-based JAR files

[ https://issues.apache.org/jira/browse/YARN-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760146#comment-13760146 ] Steve Loughran commented on YARN-1151: -- it gets more complex once you add in failure

[jira] [Updated] (YARN-1049) ContainerExistStatus should define a status for preempted containers

[ https://issues.apache.org/jira/browse/YARN-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1049: - Description: With the current behavior is impossible to determine if a container has

[jira] [Updated] (YARN-1049) ContainerExistStatus should define a status for preempted containers

[ https://issues.apache.org/jira/browse/YARN-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1049: - Attachment: YARN-1049.patch ContainerExistStatus should define a status for

[jira] [Commented] (YARN-1049) ContainerExistStatus should define a status for preempted containers

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

[jira] [Created] (YARN-1161) branch-2.1-beta compilation fails

Devaraj K created YARN-1161: --- Summary: branch-2.1-beta compilation fails Key: YARN-1161 URL: https://issues.apache.org/jira/browse/YARN-1161 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1161) branch-2.1-beta compilation fails

[ https://issues.apache.org/jira/browse/YARN-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-1161: Attachment: YARN-1161.patch branch-2.1-beta compilation fails -

[jira] [Updated] (YARN-1144) Unmanaged AMs registering a tracking URI should not be proxy-fied

[ https://issues.apache.org/jira/browse/YARN-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-1144: - Attachment: YARN-1144.patch Unmanaged AMs registering a tracking URI should not be

[jira] [Commented] (YARN-1161) branch-2.1-beta compilation fails

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

[jira] [Updated] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

[ https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated YARN-696: Attachment: YARN-696.diff Enable multiple states to to be specified in Resource Manager apps

[jira] [Commented] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760205#comment-13760205 ] Thomas Graves commented on YARN-1153: - what are the rest of your queue settings? With

[jira] [Updated] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

[ https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated YARN-696: Attachment: YARN-696.diff An invalid application state now throws a BadRequestException. I went for

[jira] [Commented] (YARN-1160) allow admins to force app deployment on a specific host

[ https://issues.apache.org/jira/browse/YARN-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760208#comment-13760208 ] Alejandro Abdelnur commented on YARN-1160: -- You can already ask for container

[jira] [Updated] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

[ https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Lorimer updated YARN-696: Attachment: YARN-696.diff Enable multiple states to to be specified in Resource Manager apps

[jira] [Created] (YARN-1162) NM auxiliary service invocations should be try/catch

Alejandro Abdelnur created YARN-1162: Summary: NM auxiliary service invocations should be try/catch Key: YARN-1162 URL: https://issues.apache.org/jira/browse/YARN-1162 Project: Hadoop YARN

[jira] [Commented] (YARN-1144) Unmanaged AMs registering a tracking URI should not be proxy-fied

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

[jira] [Commented] (YARN-1160) allow admins to force app deployment on a specific host

[ https://issues.apache.org/jira/browse/YARN-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760210#comment-13760210 ] Steve Loughran commented on YARN-1160: -- -Yes, and if you don't get that container it

[jira] [Commented] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

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

[jira] [Created] (YARN-1163) Cleanup code for AssignMapsWithLocality() in RMContainerAllocator

Junping Du created YARN-1163: Summary: Cleanup code for AssignMapsWithLocality() in RMContainerAllocator Key: YARN-1163 URL: https://issues.apache.org/jira/browse/YARN-1163 Project: Hadoop YARN

[jira] [Created] (YARN-1164) maven Junit dependency should be test only

Steve Loughran created YARN-1164: Summary: maven Junit dependency should be test only Key: YARN-1164 URL: https://issues.apache.org/jira/browse/YARN-1164 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1164) maven Junit dependency should be test only

[ https://issues.apache.org/jira/browse/YARN-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-1164: - Attachment: HADOOP-9935-001.patch Patch from André Kelpe for HADOOP-9935; this JIRA is to test

[jira] [Updated] (YARN-1152) Invalid key to HMAC computation error when getting application report for completed app attempt

[ https://issues.apache.org/jira/browse/YARN-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1152: - Target Version/s: 2.1.1-beta (was: 0.23.10, 2.1.1-beta) Affects Version/s: (was: 0.23.10) Turns

[jira] [Commented] (YARN-1159) NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL

[ https://issues.apache.org/jira/browse/YARN-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760338#comment-13760338 ] Tsuyoshi OZAWA commented on YARN-1159: -- Should we change the event

[jira] [Resolved] (YARN-1159) NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL

[ https://issues.apache.org/jira/browse/YARN-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-1159. --- Resolution: Duplicate It's a bug, and was reported before: YARN-1070. Will fix there.

[jira] [Updated] (YARN-609) Fix synchronization issues in APIs which take in lists

[ https://issues.apache.org/jira/browse/YARN-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-609: --- Attachment: YARN-609.6.patch Fix synchronization issues in APIs which take in lists

[jira] [Commented] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760408#comment-13760408 ] Jian He commented on YARN-1153: --- Exactly, the single user limit is throttling it

[jira] [Commented] (YARN-609) Fix synchronization issues in APIs which take in lists

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

[jira] [Commented] (YARN-1152) Invalid key to HMAC computation error when getting application report for completed app attempt

[ https://issues.apache.org/jira/browse/YARN-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760281#comment-13760281 ] Jason Lowe commented on YARN-1152: -- I also manually tested this on a secure cluster.

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

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

[jira] [Updated] (YARN-1001) YARN should provide per application-type and state statistics

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1001: -- Attachment: YARN-1001.2.patch Updated the patch against the latest trunk. In addition, polish the code,

[jira] [Commented] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760485#comment-13760485 ] Thomas Graves commented on YARN-1153: - sorry so why is this a bug? Its working as

[jira] [Commented] (YARN-609) Fix synchronization issues in APIs which take in lists

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

[jira] [Comment Edited] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760485#comment-13760485 ] Thomas Graves edited comment on YARN-1153 at 9/6/13 6:26 PM: -

[jira] [Resolved] (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:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-957. -- Resolution: Fixed [~devaraj.k] opened YARN-1161. Closing this.

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760436#comment-13760436 ] Omkar Vinit Joshi commented on YARN-713: rebasing patch .. had missed one local

[jira] [Updated] (YARN-609) Fix synchronization issues in APIs which take in lists

[ https://issues.apache.org/jira/browse/YARN-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-609: --- Attachment: YARN-609.8.patch Fix synchronization issues in APIs which take in lists

[jira] [Commented] (YARN-758) Augment MockNM to use multiple cores

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

[jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

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

[jira] [Updated] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-978: --- Attachment: YARN-978.5.patch [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[jira] [Updated] (YARN-1098) Separate out RM services into Always On and Active

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1098: --- Attachment: yarn-1098-4.patch Updated patch to fix javadoc and test failures.

[jira] [Commented] (YARN-1027) Implement RMHAServiceProtocol

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760582#comment-13760582 ] Karthik Kambatla commented on YARN-1027: Thanks for the detailed review, [~bikas].

[jira] [Commented] (YARN-1132) QueueMetrics.java has wrong comments

[ https://issues.apache.org/jira/browse/YARN-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760512#comment-13760512 ] Akira AJISAKA commented on YARN-1132: - Thanks for your comment, I'll close this issue

[jira] [Commented] (YARN-1098) Separate out RM services into Always On and Active

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760567#comment-13760567 ] Karthik Kambatla commented on YARN-1098: Haven't added any tests because the patch

[jira] [Resolved] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-1153. --- Resolution: Invalid CapacityScheduler queue elasticity is not working

[jira] [Resolved] (YARN-1132) QueueMetrics.java has wrong comments

[ https://issues.apache.org/jira/browse/YARN-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved YARN-1132. - Resolution: Duplicate QueueMetrics.java has wrong comments

[jira] [Commented] (YARN-1153) CapacityScheduler queue elasticity is not working

[ https://issues.apache.org/jira/browse/YARN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760510#comment-13760510 ] Jian He commented on YARN-1153: --- yh, I'm closing it. thx for clarifying

[jira] [Commented] (YARN-1001) YARN should provide per application-type and state statistics

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

[jira] [Commented] (YARN-1098) Separate out RM services into Always On and Active

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

[jira] [Updated] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-978: --- Attachment: YARN-978.6.patch [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[jira] [Commented] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760632#comment-13760632 ] Xuan Gong commented on YARN-1155: - Verified that we have test case to test this logic

[jira] [Assigned] (YARN-1162) NM auxiliary service invocations should be try/catch

[ https://issues.apache.org/jira/browse/YARN-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik reassigned YARN-1162: -- Assignee: Roman Shaposhnik NM auxiliary service invocations should be try/catch

[jira] [Resolved] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-1155. - Resolution: Invalid RM should resolve hostnames/ips in include/exclude files to support matching

[jira] [Resolved] (YARN-1162) NM auxiliary service invocations should be try/catch

[ https://issues.apache.org/jira/browse/YARN-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1162. --- Resolution: Duplicate Fix Version/s: (was: 2.1.1-beta) YARN-867 is

[jira] [Commented] (YARN-1155) RM should resolve hostnames/ips in include/exclude files to support matching against both hostnames and ips

[ https://issues.apache.org/jira/browse/YARN-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760630#comment-13760630 ] Xuan Gong commented on YARN-1155: - verified that we already have such logic: {code}

[jira] [Created] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()

Karthik Kambatla created YARN-1165: -- Summary: Move init() of activeServices to ResourceManager#serviceStart() Key: YARN-1165 URL: https://issues.apache.org/jira/browse/YARN-1165 Project: Hadoop YARN

[jira] [Updated] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()

[ https://issues.apache.org/jira/browse/YARN-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1165: --- Description: Background: # YARN-1098 separates out RM services into Always-On and Active

[jira] [Created] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

Srimanth Gunturi created YARN-1166: -- Summary: YARN 'appsFailed' metric should be of type 'counter' Key: YARN-1166 URL: https://issues.apache.org/jira/browse/YARN-1166 Project: Hadoop YARN

[jira] [Commented] (YARN-1159) NodeManager reports Invalid event: CONTAINER_KILLED_ON_REQUEST at CONTAINER_CLEANEDUP_AFTER_KILL

[ https://issues.apache.org/jira/browse/YARN-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760715#comment-13760715 ] Tsuyoshi OZAWA commented on YARN-1159: -- OK, thanks. NodeManager

[jira] [Updated] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()

[ https://issues.apache.org/jira/browse/YARN-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1165: --- Attachment: test-failures.pdf Moving creation, init() and start() of activeServices to

[jira] [Updated] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-713: --- Attachment: YARN-713.09062013.1.patch ResourceManager can exit unexpectedly if DNS is

[jira] [Updated] (YARN-609) Fix synchronization issues in APIs which take in lists

[ https://issues.apache.org/jira/browse/YARN-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-609: --- Attachment: YARN-609.7.patch Fix -1 findbug Fix synchronization issues in APIs which take in

[jira] [Reopened] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi reopened YARN-1166: Talked with [~jianhe] and [~vinodkv], and this metric should be cumulative. Hence the original

[jira] [Commented] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()

[ https://issues.apache.org/jira/browse/YARN-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760747#comment-13760747 ] Bikas Saha commented on YARN-1165: -- Are we getting the test failures even with the

[jira] [Resolved] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi resolved YARN-1166. Resolution: Not A Problem Turns out 'AppsFailed' should be interpreted as 'AppsFailing'.

[jira] [Commented] (YARN-1027) Implement RMHAServiceProtocol

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760752#comment-13760752 ] Bikas Saha commented on YARN-1027: -- RMHAProtocolService can be made available via

[jira] [Commented] (YARN-1001) YARN should provide per application-type and state statistics

[ https://issues.apache.org/jira/browse/YARN-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760460#comment-13760460 ] Zhijie Shen commented on YARN-1001: --- bq. we are expecting /ws/v1/cluster/appscount to

[jira] [Commented] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760757#comment-13760757 ] Omkar Vinit Joshi commented on YARN-1107: - Thanks Vinod.. bq. Put both

[jira] [Updated] (YARN-1027) Implement RMHAServiceProtocol

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1027: --- Attachment: yarn-1027-4.patch Patch addressing comments from Bikas.

[jira] [Updated] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-758: - Priority: Minor (was: Major) Target Version/s: 2.3.0, 2.1.1-beta

[jira] [Updated] (YARN-758) Augment MockNM to use multiple cores

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-758: - bq. This was reopened to ensure the patch was tested. Now, resolving this on the

[jira] [Commented] (YARN-1027) Implement RMHAServiceProtocol

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760774#comment-13760774 ] Karthik Kambatla commented on YARN-1027: In yarn-1027-4.patch, the RM always

[jira] [Commented] (YARN-1165) Move init() of activeServices to ResourceManager#serviceStart()

[ https://issues.apache.org/jira/browse/YARN-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760775#comment-13760775 ] Karthik Kambatla commented on YARN-1165: The current patch uploaded to YARN-1027

[jira] [Updated] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1107: Attachment: YARN-1107.20130906.1.patch Job submitted with Delegation token in secured

[jira] [Commented] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

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

[jira] [Commented] (YARN-1152) Invalid key to HMAC computation error when getting application report for completed app attempt

[ https://issues.apache.org/jira/browse/YARN-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760842#comment-13760842 ] Vinod Kumar Vavilapalli commented on YARN-1152: --- BTW, forgot to mention that,

[jira] [Created] (YARN-1167) Submitted distributed shell application shows appMasterHost = empty

Tassapol Athiapinya created YARN-1167: - Summary: Submitted distributed shell application shows appMasterHost = empty Key: YARN-1167 URL: https://issues.apache.org/jira/browse/YARN-1167 Project:

[jira] [Commented] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760870#comment-13760870 ] Omkar Vinit Joshi commented on YARN-1107: - removing locking.. Job

[jira] [Updated] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-1107: Attachment: YARN-1107.20130906.2.patch Job submitted with Delegation token in secured

[jira] [Updated] (YARN-540) Race condition causing RM to potentially relaunch already unregistered AMs on RM restart

[ https://issues.apache.org/jira/browse/YARN-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-540: - Attachment: YARN-540.4.patch Upload a patch that changes FinishApplicationMasterResponse to contain a

[jira] [Commented] (YARN-540) Race condition causing RM to potentially relaunch already unregistered AMs on RM restart

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

[jira] [Commented] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760925#comment-13760925 ] Vinod Kumar Vavilapalli commented on YARN-1107: --- +1 for the latest patch. I

[jira] [Updated] (YARN-540) Race condition causing RM to potentially relaunch already unregistered AMs on RM restart

[ https://issues.apache.org/jira/browse/YARN-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-540: - Attachment: YARN-540.5.patch New patch fixed the test case Race condition causing RM to

[jira] [Commented] (YARN-1107) Job submitted with Delegation token in secured environment causes RM to fail during RM restart

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