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

[ https://issues.apache.org/jira/browse/YARN-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1163: - Issue Type: Sub-task (was: Improvement) Parent: YARN-18 Cleanup code 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=13761723#comment-13761723 ] Steve Loughran commented on YARN-1160: -- -seems reasonable. The key thing is to ignore

[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=13761732#comment-13761732 ] Tom White commented on YARN-1144: - +1 Unmanaged AMs registering a

[jira] [Created] (YARN-1171) Add defaultQueueSchedulingPolicy to Fair Scheduler documentation

Sandy Ryza created YARN-1171: Summary: Add defaultQueueSchedulingPolicy to Fair Scheduler documentation Key: YARN-1171 URL: https://issues.apache.org/jira/browse/YARN-1171 Project: Hadoop YARN

[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=13761775#comment-13761775 ] Hudson commented on YARN-1049: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4388 (See

[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=13761780#comment-13761780 ] Hudson commented on YARN-1144: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4389 (See

[jira] [Created] (YARN-1172) Convert *SecretManagers in the RM to services

Karthik Kambatla created YARN-1172: -- Summary: Convert *SecretManagers in the RM to services Key: YARN-1172 URL: https://issues.apache.org/jira/browse/YARN-1172 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-1172) Convert *SecretManagers in the RM to services

[ https://issues.apache.org/jira/browse/YARN-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1172: --- Parent Issue: YARN-1139 (was: YARN-149) Convert *SecretManagers in the RM to services

[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=13761835#comment-13761835 ] Hudson commented on YARN-1144: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1517 (See

[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=13761832#comment-13761832 ] Hudson commented on YARN-1049: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1517 (See

[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=13761866#comment-13761866 ] Hudson commented on YARN-1049: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1543 (See

[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=13761869#comment-13761869 ] Hudson commented on YARN-1144: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1543 (See

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

[ https://issues.apache.org/jira/browse/YARN-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1163: - Attachment: YARN-1163-v1.patch Attach the first patch. Cleanup code for

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

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

[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: - Attachment: YARN-1152-2.txt Thanks for the review, Vinod. bq. We had a

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

[jira] [Created] (YARN-1173) Run -shell_command echo Hello has empty stdout

Tassapol Athiapinya created YARN-1173: - Summary: Run -shell_command echo Hello has empty stdout Key: YARN-1173 URL: https://issues.apache.org/jira/browse/YARN-1173 Project: Hadoop YARN

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762183#comment-13762183 ] Chris Trezzo commented on YARN-221: --- I have started looking at this and will hopefully

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

[jira] [Updated] (YARN-305) Too many 'Node offerred to app:... messages in RM

[ https://issues.apache.org/jira/browse/YARN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-305: -- Attachment: YARN-305.2.patch Sorry, somehow missed review comments in email. These are the only

[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-5.patch Rebased on trunk. Mimicked the changes from YARN-1107, and

[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=13762136#comment-13762136 ] Karthik Kambatla commented on YARN-1098: bq. Unrelated. Why are the secret manager

[jira] [Updated] (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 ] Akira AJISAKA updated YARN-1166: Attachment: YARN-1166.patch I agree to the original request. I attached a patch for type 'counter'.

[jira] [Commented] (YARN-1174) Accessing task page for running job throw 500 Error code

[ https://issues.apache.org/jira/browse/YARN-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762259#comment-13762259 ] Paul Han commented on YARN-1174: Patch is available. Will upload for review soon.

[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=13762310#comment-13762310 ] Vinod Kumar Vavilapalli commented on YARN-1152: --- +1, looks good. Checking

[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=13762268#comment-13762268 ] Bikas Saha commented on YARN-540: - getIsUnregistered() instead of getUnregistered() ?

[jira] [Updated] (YARN-1025) ResourceManager and NodeManager do not load native libraries on Windows.

[ https://issues.apache.org/jira/browse/YARN-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-1025: Attachment: YARN-1025.1.patch I'm attaching a patch that updates yarn.cmd to set java.library.path,

[jira] [Created] (YARN-1176) RM web services ClusterMetricsInfo total nodes doesn't include unhealthy nodes

Thomas Graves created YARN-1176: --- Summary: RM web services ClusterMetricsInfo total nodes doesn't include unhealthy nodes Key: YARN-1176 URL: https://issues.apache.org/jira/browse/YARN-1176 Project:

[jira] [Created] (YARN-1174) Accessing task page for running job throw 500 Error code

Paul Han created YARN-1174: -- Summary: Accessing task page for running job throw 500 Error code Key: YARN-1174 URL: https://issues.apache.org/jira/browse/YARN-1174 Project: Hadoop YARN Issue Type:

[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=13762337#comment-13762337 ] Vinod Kumar Vavilapalli commented on YARN-910: -- Okay, looks good. Checking this

[jira] [Created] (YARN-1177) Support automatic failover using ZKFC

Karthik Kambatla created YARN-1177: -- Summary: Support automatic failover using ZKFC Key: YARN-1177 URL: https://issues.apache.org/jira/browse/YARN-1177 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1025) ResourceManager and NodeManager do not load native libraries on Windows.

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

[jira] [Commented] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762370#comment-13762370 ] Jason Lowe commented on YARN-1175: -- I believe there's a trailing newline character in the

[jira] [Commented] (YARN-1025) ResourceManager and NodeManager do not load native libraries on Windows.

[ https://issues.apache.org/jira/browse/YARN-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762369#comment-13762369 ] Chris Nauroth commented on YARN-1025: - {quote} -1 tests included. The patch doesn't

[jira] [Commented] (YARN-305) Too many 'Node offerred to app:... messages in RM

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

[jira] [Commented] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762375#comment-13762375 ] Tassapol Athiapinya commented on YARN-1175: --- I understand that point. As an end

[jira] [Commented] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762379#comment-13762379 ] Tassapol Athiapinya commented on YARN-1175: --- Also, for distributed shell 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=13762356#comment-13762356 ] Alejandro Abdelnur commented on YARN-910: - [~vinodkv], thanks. Any reason not have

[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=13762359#comment-13762359 ] Hudson commented on YARN-910: - SUCCESS: Integrated in Hadoop-trunk-Commit #4391 (See

[jira] [Commented] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762388#comment-13762388 ] Jason Lowe commented on YARN-1175: -- It is consistent with the contents of the log. If

[jira] [Resolved] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya resolved YARN-1175. --- Resolution: Not A Problem It works as intended. LogLength shown in

[jira] [Commented] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

[ https://issues.apache.org/jira/browse/YARN-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762391#comment-13762391 ] Tassapol Athiapinya commented on YARN-1175: --- Thank you [~jlowe] for

[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=13762323#comment-13762323 ] Hudson commented on YARN-1152: -- SUCCESS: Integrated in Hadoop-trunk-Commit #4390 (See

[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.9.patch Fix synchronization issues in APIs which take in lists

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13762331#comment-13762331 ] Hadoop QA commented on YARN-1166: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762411#comment-13762411 ] Jonathan Eagles commented on YARN-649: -- [~sandyr]

[jira] [Created] (YARN-1178) TestContainerLogsPage#testContainerLogPageAccess is failing

Jonathan Eagles created YARN-1178: - Summary: TestContainerLogsPage#testContainerLogPageAccess is failing Key: YARN-1178 URL: https://issues.apache.org/jira/browse/YARN-1178 Project: Hadoop YARN

[jira] [Created] (YARN-1175) LogLength shown in $ yarn logs is 1 character longer than actual stdout

Tassapol Athiapinya created YARN-1175: - Summary: LogLength shown in $ yarn logs is 1 character longer than actual stdout Key: YARN-1175 URL: https://issues.apache.org/jira/browse/YARN-1175

[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=13762550#comment-13762550 ] Karthik Kambatla commented on YARN-1165: I figured a way around this. Details: #

[jira] [Reopened] (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 reopened YARN-1165: Move init() of activeServices to ResourceManager#serviceStart()

[jira] [Resolved] (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 resolved YARN-1165. Resolution: Not A Problem My bad. We should close this as Not A Problem as we are not

[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-5.patch Thanks Bikas. I am uploading a patch that addresses all your

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

[ https://issues.apache.org/jira/browse/YARN-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762557#comment-13762557 ] Karthik Kambatla commented on YARN-1027: bq. What happens if we call this method

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

[ https://issues.apache.org/jira/browse/YARN-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762565#comment-13762565 ] Vinod Kumar Vavilapalli commented on YARN-292: -- Actually, I am able to

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

[jira] [Resolved] (YARN-1173) Run -shell_command echo Hello has empty stdout

[ https://issues.apache.org/jira/browse/YARN-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya resolved YARN-1173. --- Resolution: Invalid It is invalid usage. Distributed shell user has to separate

[jira] [Updated] (YARN-1168) Cannot run echo \Hello World\

[ https://issues.apache.org/jira/browse/YARN-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya updated YARN-1168: -- Description: Run $ ssh localhost echo \Hello World\ with bash does succeed. Hello World

[jira] [Commented] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

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

[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=13762599#comment-13762599 ] Bikas Saha commented on YARN-540: - bq. Exception because unManagedAM attempt will be

[jira] [Assigned] (YARN-921) Consider adding clone methods to protocol objects

[ https://issues.apache.org/jira/browse/YARN-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-921: --- Assignee: Junping Du Consider adding clone methods to protocol objects

[jira] [Commented] (YARN-921) Consider adding clone methods to protocol objects

[ https://issues.apache.org/jira/browse/YARN-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762610#comment-13762610 ] Bikas Saha commented on YARN-921: - Before we proceed to invest effort in this jira, it may

[jira] [Commented] (YARN-921) Consider adding clone methods to protocol objects

[ https://issues.apache.org/jira/browse/YARN-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762661#comment-13762661 ] Junping Du commented on YARN-921: - Hi Bikas, Thanks for your good suggestions here. I would

[jira] [Updated] (YARN-291) [Umbrella] 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: Summary: [Umbrella] Dynamic resource configuration (was: Dynamic resource configuration) [Umbrella]

[jira] [Commented] (YARN-921) Consider adding clone methods to protocol objects

[ https://issues.apache.org/jira/browse/YARN-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762756#comment-13762756 ] Bikas Saha commented on YARN-921: - The requirement is to be able to clone a yarn protocol

[jira] [Updated] (YARN-1042) add ability to specify affinity/anti-affinity in container requests

[ https://issues.apache.org/jira/browse/YARN-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1042: - Attachment: YARN-1042-demo.patch add ability to specify affinity/anti-affinity in container requests