[jira] [Commented] (YARN-2241) ZKRMStateStore: On startup, show nicer messages when znodes already exist

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

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049758#comment-14049758 ] Steve Loughran commented on YARN-2139: -- looks a good first draft # unless this does

[jira] [Updated] (YARN-2246) Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[ https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2246: -- Component/s: webapp Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[jira] [Moved] (YARN-2246) Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[ https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen moved MAPREDUCE-4064 to YARN-2246: -- Component/s: (was: mrv2) Affects Version/s: (was:

[jira] [Commented] (YARN-2246) Job History Link in RM UI is redirecting to the URL which contains Job Id twice

[ https://issues.apache.org/jira/browse/YARN-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049813#comment-14049813 ] Zhijie Shen commented on YARN-2246: --- Move the ticket to YARN, as the root cause sound

[jira] [Updated] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2233: Attachment: apache-yarn-2233.1.patch {quote} 1. bq. It should be noted that when cancelling a

[jira] [Assigned] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

[ https://issues.apache.org/jira/browse/YARN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K reassigned YARN-2243: --- Assignee: Devaraj K Good catch [~yuzhih...@gmail.com]. Order of arguments for

[jira] [Updated] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

[ https://issues.apache.org/jira/browse/YARN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-2243: Attachment: YARN-2243.patch Attaching trivial patch to fix this issue. Order of arguments for

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

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

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049839#comment-14049839 ] Tsuyoshi OZAWA commented on YARN-2242: -- [~zjshen], thank you for the notification. I

[jira] [Commented] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

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

[jira] [Updated] (YARN-2013) The diagnostics is always the ExitCodeException stack when the container crashes

[ https://issues.apache.org/jira/browse/YARN-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2013: - Attachment: YARN-2013.3-2.patch Attached same patch for confirming that the patch doesn't have

[jira] [Commented] (YARN-2013) The diagnostics is always the ExitCodeException stack when the container crashes

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

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049864#comment-14049864 ] Sunil G commented on YARN-2022: --- Thank you Mayank, Vinod and Wangda Tan for the reviews.

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

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

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2243) Order of arguments for Preconditions.checkNotNull() is wrong in SchedulerApplicationAttempt ctor

[ https://issues.apache.org/jira/browse/YARN-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049959#comment-14049959 ] Ted Yu commented on YARN-2243: -- Thanks for taking care of this. Order of arguments for

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

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

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

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

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050042#comment-14050042 ] Zhijie Shen commented on YARN-2233: --- Almost good to me. Just some nits: 1. This won't

[jira] [Updated] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2065: - Attachment: YARN-2065-003.patch correction: this is the version that compiles against trunk.

[jira] [Commented] (YARN-675) In YarnClient, pull AM logs on AM container failure

[ https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050260#comment-14050260 ] Zhijie Shen commented on YARN-675: -- Sure, reassign it to you In YarnClient, pull AM logs

[jira] [Updated] (YARN-675) In YarnClient, pull AM logs on AM container failure

[ https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-675: - Assignee: Li Lu (was: Zhijie Shen) In YarnClient, pull AM logs on AM container failure

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

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

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

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

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050286#comment-14050286 ] Jian He commented on YARN-2065: --- thanks for the testing, Steve! AM cannot create new

[jira] [Updated] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

[ https://issues.apache.org/jira/browse/YARN-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2211: Attachment: YARN-2211.1.patch RMStateStore needs to save AMRMToken master key for recovery when RM

[jira] [Updated] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

[ https://issues.apache.org/jira/browse/YARN-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2208: Attachment: YARN-2208.2.patch AMRMTokenManager need to have a way to roll over AMRMToken

[jira] [Updated] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

[ https://issues.apache.org/jira/browse/YARN-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2212: Attachment: YARN-2212.1.patch ApplicationMaster needs to find a way to update the AMRMToken periodically

[jira] [Updated] (YARN-2237) MRAppMaster changes for AMRMToken roll-up

[ https://issues.apache.org/jira/browse/YARN-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2237: Attachment: YARN-2237.1.patch MRAppMaster changes for AMRMToken roll-up

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050301#comment-14050301 ] Wei Yan commented on YARN-2139: --- Thanks for the comments, [~ste...@apache.org]. For you

[jira] [Commented] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

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

[jira] [Updated] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

[ https://issues.apache.org/jira/browse/YARN-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2208: Attachment: YARN-2208.3.patch Fix findbugs and testcase failures AMRMTokenManager need to have a way to

[jira] [Updated] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

[ https://issues.apache.org/jira/browse/YARN-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2211: Attachment: YARN-2211.2.patch RMStateStore needs to save AMRMToken master key for recovery when RM

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

[ https://issues.apache.org/jira/browse/YARN-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050521#comment-14050521 ] Steve Loughran commented on YARN-2065: -- With Jenkins happy, I'm +1 on this patch; it

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050530#comment-14050530 ] Karthik Kambatla commented on YARN-2139: bq. this is really disk io bandwidth, so

[jira] [Commented] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050533#comment-14050533 ] Anubhav Dhoot commented on YARN-2175: - We have seen it happen when the source file

[jira] [Commented] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050539#comment-14050539 ] Karthik Kambatla commented on YARN-2175: I ll let Anubhav provide details on the

[jira] [Commented] (YARN-2175) Container localization has no timeouts and tasks can be stuck there for a long time

[ https://issues.apache.org/jira/browse/YARN-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050543#comment-14050543 ] Karthik Kambatla commented on YARN-2175: In MR1, mapred.task.timeout handles

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050556#comment-14050556 ] Varun Vasudev commented on YARN-2233: - The test case failure is due to YARN-2232. It

[jira] [Commented] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used

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

[jira] [Updated] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2233: Attachment: apache-yarn-2233.2.patch {quote} 1. This won't happen inside renewDelegationToken, as

[jira] [Commented] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

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

[jira] [Commented] (YARN-2240) yarn logs can get corrupted if the aggregator does not have permissions to the log file it tries to read

[ https://issues.apache.org/jira/browse/YARN-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050580#comment-14050580 ] Mit Desai commented on YARN-2240: - Aggregated Logs Comment [~vinodkv], here is the error

[jira] [Commented] (YARN-2241) ZKRMStateStore: On startup, show nicer messages when znodes already exist

[ https://issues.apache.org/jira/browse/YARN-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050621#comment-14050621 ] Karthik Kambatla commented on YARN-2241: +1 ZKRMStateStore: On startup, show

[jira] [Created] (YARN-2247) Allow RM web services users to authenticate using delegation tokens

Varun Vasudev created YARN-2247: --- Summary: Allow RM web services users to authenticate using delegation tokens Key: YARN-2247 URL: https://issues.apache.org/jira/browse/YARN-2247 Project: Hadoop YARN

[jira] [Updated] (YARN-2247) Allow RM web services users to authenticate using delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2247: Attachment: apache-yarn-2247.0.patch Allow RM web services users to authenticate using delegation

[jira] [Updated] (YARN-2241) ZKRMStateStore: On startup, show nicer messages if znodes already exist

[ https://issues.apache.org/jira/browse/YARN-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2241: --- Summary: ZKRMStateStore: On startup, show nicer messages if znodes already exist (was:

[jira] [Commented] (YARN-2241) ZKRMStateStore: On startup, show nicer messages if znodes already exist

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

[jira] [Created] (YARN-2248) Capacity Scheduler changes for moving apps between queues

Janos Matyas created YARN-2248: -- Summary: Capacity Scheduler changes for moving apps between queues Key: YARN-2248 URL: https://issues.apache.org/jira/browse/YARN-2248 Project: Hadoop YARN

[jira] [Commented] (YARN-2248) Capacity Scheduler changes for moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050729#comment-14050729 ] Vinod Kumar Vavilapalli commented on YARN-2248: --- Do you mind attaching a

[jira] [Assigned] (YARN-2248) Capacity Scheduler changes for moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-2248: - Assignee: Janos Matyas [~matyix], tx for opening this. Assigning it to

[jira] [Commented] (YARN-2232) ClientRMService doesn't allow delegation token owner to cancel their own token in secure mode

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

[jira] [Commented] (YARN-2232) ClientRMService doesn't allow delegation token owner to cancel their own token in secure mode

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

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115.patch Hi [~djp], in this new patch I modified an existing unit test, on testing

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115-1.patch Better interface design for the private verification function on diagnostic

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

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

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

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

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

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

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: (was: YARN-2229.3.patch) Making ContainerId long type

[jira] [Created] (YARN-2249) AM resync may send container release request before container is actually recovered

Jian He created YARN-2249: - Summary: AM resync may send container release request before container is actually recovered Key: YARN-2249 URL: https://issues.apache.org/jira/browse/YARN-2249 Project: Hadoop

[jira] [Updated] (YARN-2249) AM resync may send container release request before container is actually recovered

[ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2249: -- Description: AM resync on RM restart will send outstanding resource requests, container release list etc. back

[jira] [Updated] (YARN-2249) RM may receive container release request on AM resync before container is actually recovered

[ https://issues.apache.org/jira/browse/YARN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2249: -- Summary: RM may receive container release request on AM resync before container is actually recovered (was: AM

[jira] [Updated] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-2069: Attachment: YARN-2069-trunk-3.patch Rebasing and Updating the patch. Thanks, Mayank Add

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050913#comment-14050913 ] Jian He commented on YARN-1366: --- looks good, +1 AM should implement Resync with the

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.3.patch Making ContainerId long type

[jira] [Commented] (YARN-2229) Making ContainerId long type

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

[jira] [Commented] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue

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

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050961#comment-14050961 ] Tsuyoshi OZAWA commented on YARN-2229: -- [~jianhe], can you check whether trunk code

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050965#comment-14050965 ] Bikas Saha commented on YARN-1366: -- Why are we returning the old allocateResponse to the

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050975#comment-14050975 ] Jian He commented on YARN-1366: --- bq. Should we make a second call to allocate (after

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050977#comment-14050977 ] Jian He commented on YARN-1366: --- bq. in which case the returned allocate response should be

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050978#comment-14050978 ] Bikas Saha commented on YARN-1366: -- Does a null response make sense for the user? AM

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050990#comment-14050990 ] Jian He commented on YARN-2229: --- it failed with cannot find symbol for this method

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051013#comment-14051013 ] Rohith commented on YARN-1366: -- bq. can you add some documentation about this Shall I add in

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051019#comment-14051019 ] Junping Du commented on YARN-2242: -- Patch looks good to me overall. Some minor fix is

[jira] [Commented] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051045#comment-14051045 ] Tsuyoshi OZAWA commented on YARN-2229: -- Thanks you, Jian. I found that

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051049#comment-14051049 ] Jian He commented on YARN-1366: --- add java doc for AMRMClient#allocate(). should be enough.

[jira] [Updated] (YARN-2229) Making ContainerId long type

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.4.patch Updated a patch not to use Long.compare(long, long). Making

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

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

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051068#comment-14051068 ] Li Lu commented on YARN-2242: - Thanks [~djp]! Improve exception information on AM launch

[jira] [Commented] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14051066#comment-14051066 ] Junping Du commented on YARN-2242: -- bq. Zhijie Shen, thank you for the notification. I

[jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes

[ https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: Attachment: YARN-2242-070115-2.patch Add the missing period in the end of the diagnostic information. Improve

[jira] [Updated] (YARN-2062) Too many InvalidStateTransitionExceptions from NodeState.NEW on RM failover

[ https://issues.apache.org/jira/browse/YARN-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2062: --- Target Version/s: 2.6.0 (was: 2.5.0) Too many InvalidStateTransitionExceptions from

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

[ https://issues.apache.org/jira/browse/YARN-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1354: --- Target Version/s: 2.6.0 (was: 2.5.0) Recover applications upon nodemanager restart

[jira] [Updated] (YARN-1342) Recover container tokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1342: --- Target Version/s: 2.6.0 (was: 2.5.0) Recover container tokens upon nodemanager restart

[jira] [Updated] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2110: --- Target Version/s: 2.6.0 (was: 2.5.0) TestAMRestart#testAMRestartWithExistingContainers

[jira] [Updated] (YARN-1106) The RM should point the tracking url to the RM app page if its empty

[ https://issues.apache.org/jira/browse/YARN-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1106: --- Target Version/s: 2.6.0 (was: 3.0.0, 2.5.0) The RM should point the tracking url to the RM

[jira] [Updated] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1408: --- Target Version/s: 2.6.0 (was: 2.5.0) Preemption caused Invalid State Event: ACQUIRED at

[jira] [Updated] (YARN-1856) cgroups based memory monitoring for containers

[ https://issues.apache.org/jira/browse/YARN-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1856: --- Target Version/s: 2.6.0 (was: 2.5.0) cgroups based memory monitoring for containers

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1809: --- Target Version/s: 2.6.0 (was: 2.5.0) Synchronize RM and Generic History Service Web-UIs

[jira] [Updated] (YARN-1844) yarn.log.server.url should have a default value

[ https://issues.apache.org/jira/browse/YARN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1844: --- Target Version/s: 2.6.0 (was: 2.5.0) yarn.log.server.url should have a default value

[jira] [Updated] (YARN-1681) When banned.users is not set in LCE's container-executor.cfg, submit job with user in DEFAULT_BANNED_USERS will receive unclear error message

[ https://issues.apache.org/jira/browse/YARN-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1681: --- Target Version/s: 2.6.0 (was: 2.5.0) When banned.users is not set in LCE's

[jira] [Updated] (YARN-2157) Document YARN metrics

[ https://issues.apache.org/jira/browse/YARN-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2157: --- Target Version/s: 2.6.0 (was: 2.5.0) Document YARN metrics -

[jira] [Updated] (YARN-2162) Fair Scheduler :ability to optionally configure minResources and maxResources in terms of percentage

[ https://issues.apache.org/jira/browse/YARN-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2162: --- Target Version/s: 2.6.0 (was: 2.5.0) Fair Scheduler :ability to optionally configure

[jira] [Updated] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2209: --- Target Version/s: 2.6.0 (was: 2.5.0) Replace allocate#resync command with

  1   2   >