[jira] [Updated] (YARN-1932) Javascript injection on the job status page

[ https://issues.apache.org/jira/browse/YARN-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1932: Priority: Blocker (was: Critical) Javascript injection on the job status page

[jira] [Assigned] (YARN-1935) Security for timeline service

[ https://issues.apache.org/jira/browse/YARN-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-1935: - Assignee: Zhijie Shen Security for timeline service -

[jira] [Commented] (YARN-1935) Security for timeline service

[ https://issues.apache.org/jira/browse/YARN-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968121#comment-13968121 ] Zhijie Shen commented on YARN-1935: --- I'm going to take care of the security issues of the

[jira] [Updated] (YARN-1935) Security for timeline server

[ https://issues.apache.org/jira/browse/YARN-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1935: -- Summary: Security for timeline server (was: Security for timeline service) Security for timeline

[jira] [Updated] (YARN-1935) Security for timeline service

[ https://issues.apache.org/jira/browse/YARN-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1935: -- Issue Type: New Feature (was: Sub-task) Parent: (was: YARN-1530) Security for timeline

[jira] [Commented] (YARN-996) REST API support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968123#comment-13968123 ] Kenji Kikushima commented on YARN-996: -- [~tgraves], thanks for your comment. Certainly,

[jira] [Created] (YARN-1936) Secured timeline client

Zhijie Shen created YARN-1936: - Summary: Secured timeline client Key: YARN-1936 URL: https://issues.apache.org/jira/browse/YARN-1936 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-1937) Access control of per-framework data

Zhijie Shen created YARN-1937: - Summary: Access control of per-framework data Key: YARN-1937 URL: https://issues.apache.org/jira/browse/YARN-1937 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-1938) Kerberos authentication for the timeline server

Zhijie Shen created YARN-1938: - Summary: Kerberos authentication for the timeline server Key: YARN-1938 URL: https://issues.apache.org/jira/browse/YARN-1938 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-996) REST API support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968165#comment-13968165 ] Junping Du commented on YARN-996: - Thanks both for good points on adding check ACL for this

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968211#comment-13968211 ] Rohith commented on YARN-1861: -- Oops, I too encounterd with both RM is standy by state forever

[jira] [Commented] (YARN-1933) TestAMRestart and TestNodeHealthService failing sometimes on Windows

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

[jira] [Commented] (YARN-1928) TestAMRMRPCNodeUpdates fails ocassionally

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

[jira] [Commented] (YARN-1928) TestAMRMRPCNodeUpdates fails ocassionally

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

[jira] [Commented] (YARN-1933) TestAMRestart and TestNodeHealthService failing sometimes on Windows

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

[jira] [Updated] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1929: --- Attachment: yarn-1929-1.patch Here is a first-cut patch that removes unnecessary

[jira] [Commented] (YARN-1928) TestAMRMRPCNodeUpdates fails ocassionally

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

[jira] [Commented] (YARN-1933) TestAMRestart and TestNodeHealthService failing sometimes on Windows

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

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968448#comment-13968448 ] Tsuyoshi OZAWA commented on YARN-1929: -- Thinking about the best way to write a unit

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

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

[jira] [Updated] (YARN-1337) Recover active container state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1337: --- Assignee: (was: Ravi Prakash) Recover active container state upon nodemanager restart

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968487#comment-13968487 ] Tsuyoshi OZAWA commented on YARN-1861: -- [~kasha], I think this problem looks very

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968480#comment-13968480 ] Mit Desai commented on YARN-1281: - [~kasha], are you still seeing this test failing?

[jira] [Assigned] (YARN-1355) Recover application ACLs upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-1355: Assignee: Jason Lowe Recover application ACLs upon nodemanager restart

[jira] [Assigned] (YARN-1354) Recover applications upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-1354: Assignee: Jason Lowe Recover applications upon nodemanager restart

[jira] [Assigned] (YARN-1352) Recover LogAggregationService upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-1352: Assignee: Jason Lowe Recover LogAggregationService upon nodemanager restart

[jira] [Assigned] (YARN-1337) Recover active container state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-1337: Assignee: Jason Lowe Recover active container state upon nodemanager restart

[jira] [Commented] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968501#comment-13968501 ] Karthik Kambatla commented on YARN-1281: Yes. Almost in every nightly run. I have

[jira] [Updated] (YARN-1281) TestZKRMStateStoreZKClientConnections fails intermittently

[ https://issues.apache.org/jira/browse/YARN-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1281: --- Assignee: (was: Karthik Kambatla) TestZKRMStateStoreZKClientConnections fails

[jira] [Created] (YARN-1939) Improve the packaging of AmIpFilter

Thomas Graves created YARN-1939: --- Summary: Improve the packaging of AmIpFilter Key: YARN-1939 URL: https://issues.apache.org/jira/browse/YARN-1939 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968520#comment-13968520 ] Tsuyoshi OZAWA commented on YARN-1861: -- Thank you for pointing, Karthik. I'll continue

[jira] [Commented] (YARN-1897) Define SignalContainerRequest and SignalContainerResponse

[ https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968521#comment-13968521 ] Xuan Gong commented on YARN-1897: - [~mingma] bq. For SignalContainerResponse, what is the

[jira] [Commented] (YARN-1939) Improve the packaging of AmIpFilter

[ https://issues.apache.org/jira/browse/YARN-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968531#comment-13968531 ] Thomas Graves commented on YARN-1939: - Looks like I was mistaken. the web proxy is

[jira] [Resolved] (YARN-1939) Improve the packaging of AmIpFilter

[ https://issues.apache.org/jira/browse/YARN-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves resolved YARN-1939. - Resolution: Invalid Improve the packaging of AmIpFilter ---

[jira] [Commented] (YARN-1897) Define SignalContainerRequest and SignalContainerResponse

[ https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968544#comment-13968544 ] Ming Ma commented on YARN-1897: --- Sounds good. How about IsCMDSubmissionCompleted? Define

[jira] [Commented] (YARN-435) Make it easier to access cluster topology information in an AM

[ https://issues.apache.org/jira/browse/YARN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968558#comment-13968558 ] Bikas Saha commented on YARN-435: - Pasting the description from YARN-1722 that was closed as

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968653#comment-13968653 ] Steve Loughran commented on YARN-1929: -- I'm +1 to the change to composite service, as

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968659#comment-13968659 ] Jian He commented on YARN-1879: --- RetryCache is used to handle retries at *RPC level* to

[jira] [Updated] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1929: --- Attachment: yarn-1929-2.patch Here is a new patch that adds a test. Thanks Steve for taking

[jira] [Commented] (YARN-558) Add ability to completely remove nodemanager from resourcemanager.

[ https://issues.apache.org/jira/browse/YARN-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968800#comment-13968800 ] Christian Smith commented on YARN-558: -- +1 For this as well. This is essential for

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968808#comment-13968808 ] Karthik Kambatla commented on YARN-1929: bq. Now, there is one little quirk by

[jira] [Commented] (YARN-1927) Preemption message shouldn’t be created multiple times for same container-id in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968830#comment-13968830 ] Carlo Curino commented on YARN-1927: I agree with Chris's explanation, we are

[jira] [Created] (YARN-1940) deleteAsUser() terminates early without deleting more files on error

Kihwal Lee created YARN-1940: Summary: deleteAsUser() terminates early without deleting more files on error Key: YARN-1940 URL: https://issues.apache.org/jira/browse/YARN-1940 Project: Hadoop YARN

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

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

[jira] [Resolved] (YARN-1190) enabling uber mode with 0 reducer still requires mapreduce.reduce.memory.mb to be less than yarn.app.mapreduce.am.resource.mb

[ https://issues.apache.org/jira/browse/YARN-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-1190. --- Resolution: Duplicate Assignee: Siqi Li enabling uber mode with 0 reducer still requires

[jira] [Updated] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sietse T. Au updated YARN-1902: --- Affects Version/s: 2.4.0 Allocation of too many containers when a second request is done with the

[jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968906#comment-13968906 ] Siqi Li commented on YARN-1391: --- I think this patch can still be applied to the trunk Lost

[jira] [Resolved] (YARN-1415) In scheduler UI, including used memory in Memory Total seems to be inaccurate

[ https://issues.apache.org/jira/browse/YARN-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-1415. --- Resolution: Not a Problem In scheduler UI, including used memory in Memory Total seems to be inaccurate

[jira] [Commented] (YARN-1414) with Fair Scheduler reserved MB in WebUI is leaking when killing waiting jobs

[ https://issues.apache.org/jira/browse/YARN-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968909#comment-13968909 ] Siqi Li commented on YARN-1414: --- For now, this patch is able to update leaf queues and root

[jira] [Commented] (YARN-1929) DeadLock in RM when automatic failover is enabled.

[ https://issues.apache.org/jira/browse/YARN-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968966#comment-13968966 ] Jian He commented on YARN-1929: --- patch looks good to me, wait for others to also take a look.

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968965#comment-13968965 ] Karthik Kambatla commented on YARN-1934: Ideally, we should guard against accessing

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968967#comment-13968967 ] Karthik Kambatla commented on YARN-1934: Or, move all uses to runWithCheck().

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968980#comment-13968980 ] Jian He commented on YARN-1934: --- I think we should have all uses of zkClient with

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968987#comment-13968987 ] Karthik Kambatla commented on YARN-1934: Working on a patch, will try to post

[jira] [Updated] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1934: --- Priority: Blocker (was: Critical) Potential NPE in ZKRMStateStore caused by handling

[jira] [Updated] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1934: --- Attachment: yarn-1934-0.patch Here is a patch that replaces all direct references to zkClient

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

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

[jira] [Commented] (YARN-1934) Potential NPE in ZKRMStateStore caused by handling Disconnected event from ZK.

[ https://issues.apache.org/jira/browse/YARN-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969225#comment-13969225 ] Rohith commented on YARN-1934: -- +1 patch looks good to me :-) Potential NPE in