[jira] [Commented] (YARN-3760) FSDataOutputStream leak in AggregatedLogFormat.LogWriter.close()

[ https://issues.apache.org/jira/browse/YARN-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959880#comment-15959880 ] Junping Du commented on YARN-3760: -- YARN-6288 just get checked in, so patch doesn't apply

[jira] [Commented] (YARN-3760) FSDataOutputStream leak in AggregatedLogFormat.LogWriter.close()

[ https://issues.apache.org/jira/browse/YARN-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959756#comment-15959756 ] Junping Du commented on YARN-3760: -- Patch LGTM. Will commit it shortly. > FSDataOutputStr

[jira] [Commented] (YARN-5748) Backport YARN-5718 to branch-2

[ https://issues.apache.org/jira/browse/YARN-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955488#comment-15955488 ] Junping Du commented on YARN-5748: -- Thanks [~iwasakims] for taking this up. I will review

[jira] [Assigned] (YARN-5748) Backport YARN-5718 to branch-2

[ https://issues.apache.org/jira/browse/YARN-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-5748: Assignee: Masatake Iwasaki (was: Junping Du) > Backport YARN-5718 to branch-2 > ---

[jira] [Commented] (YARN-5418) When partial log aggregation is enabled, display the list of aggregated files on the container log page

[ https://issues.apache.org/jira/browse/YARN-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954242#comment-15954242 ] Junping Du commented on YARN-5418: -- {noformat} Processing: YARN-5418 YARN-5418 patch is be

[jira] [Commented] (YARN-5418) When partial log aggregation is enabled, display the list of aggregated files on the container log page

[ https://issues.apache.org/jira/browse/YARN-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954244#comment-15954244 ] Junping Du commented on YARN-5418: -- The latest test run is: https://builds.apache.org/job

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951458#comment-15951458 ] Junping Du commented on YARN-6265: -- The patch looks mostly fine. About the message, actual

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951408#comment-15951408 ] Junping Du commented on YARN-6265: -- Sorry for coming late on this. I will review it today!

[jira] [Commented] (YARN-5418) When partial log aggregation is enabled, display the list of aggregated files on the container log page

[ https://issues.apache.org/jira/browse/YARN-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949884#comment-15949884 ] Junping Du commented on YARN-5418: -- Thanks [~xgong] for the patch. The jenkins sounds have

[jira] [Updated] (YARN-6200) Revert YARN-5068

[ https://issues.apache.org/jira/browse/YARN-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6200: - Fix Version/s: (was: 2.8.1) > Revert YARN-5068 > > > Key: YARN-6200 >

[jira] [Updated] (YARN-6153) keepContainer does not work when AM retry window is set

[ https://issues.apache.org/jira/browse/YARN-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6153: - Target Version/s: 2.8.1, 3.0.0-alpha3 (was: 2.8.0, 3.0.0-alpha3) > keepContainer does not work when AM ret

[jira] [Updated] (YARN-6102) On failover RM can crash due to unregistered event to AsyncDispatcher

[ https://issues.apache.org/jira/browse/YARN-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6102: - Target Version/s: 2.8.1 (was: 2.8.0) > On failover RM can crash due to unregistered event to AsyncDispatch

[jira] [Updated] (YARN-6367) YARN logs CLI needs alway check containerLogsInfo/containerLogInfo before parse the JSON object from NMWebService

[ https://issues.apache.org/jira/browse/YARN-6367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6367: - Fix Version/s: 3.0.0-alpha3 > YARN logs CLI needs alway check containerLogsInfo/containerLogInfo before >

[jira] [Commented] (YARN-6367) YARN logs CLI needs alway check containerLogsInfo/containerLogInfo before parse the JSON object from NMWebService

[ https://issues.apache.org/jira/browse/YARN-6367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934090#comment-15934090 ] Junping Du commented on YARN-6367: -- Patch LGTM. +1. Will commit it shortly. > YARN logs C

[jira] [Updated] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5068: - Fix Version/s: (was: 2.8.0) > Expose scheduler queue to application master > --

[jira] [Updated] (YARN-3126) FairScheduler: queue's usedResource is always more than the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3126: - Fix Version/s: (was: 2.8.0) > FairScheduler: queue's usedResource is always more than the maxResource l

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927010#comment-15927010 ] Junping Du commented on YARN-6336: -- I believe someone triggered already. Anyway, I think i

[jira] [Comment Edited] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926766#comment-15926766 ] Junping Du edited comment on YARN-6336 at 3/15/17 6:54 PM: --- bq. A

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926766#comment-15926766 ] Junping Du commented on YARN-6336: -- bq. Any committer helps to retrigger YARN-6326 Hadoop-

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926763#comment-15926763 ] Junping Du commented on YARN-6336: -- Filed YETUS-495. > Jenkins report YARN new UI build f

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926755#comment-15926755 ] Junping Du commented on YARN-6336: -- bq. One thing I observed now is the link of compile re

[jira] [Updated] (YARN-6294) ATS client should better handle Socket closed case

[ https://issues.apache.org/jira/browse/YARN-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6294: - Fix Version/s: 3.0.0-alpha3 > ATS client should better handle Socket closed case >

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926657#comment-15926657 ] Junping Du commented on YARN-6336: -- Do you mean above compile failed is without the patch?

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926613#comment-15926613 ] Junping Du commented on YARN-6336: -- Hi [~rohithsharma] and [~sunilg], from Jenkins report

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925381#comment-15925381 ] Junping Du commented on YARN-6265: -- bq. Does jenkins have any issue? Hi [~yuanbo], it cou

[jira] [Commented] (YARN-5369) Improve Yarn logs command to get container logs based on Node Id

[ https://issues.apache.org/jira/browse/YARN-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925193#comment-15925193 ] Junping Du commented on YARN-5369: -- Hi [~xgong], sorry for coming late on this. Do we stil

[jira] [Commented] (YARN-6294) ATS client should better handle Socket closed case

[ https://issues.apache.org/jira/browse/YARN-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925057#comment-15925057 ] Junping Du commented on YARN-6294: -- +1. Will commit it shortly. > ATS client should bette

[jira] [Commented] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is still running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924896#comment-15924896 ] Junping Du commented on YARN-6313: -- Filed YARN-6336 to address YARN new UI build failure.

[jira] [Updated] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is still running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6313: - Fix Version/s: 3.0.0-alpha3 > yarn logs cli should provide logs for a completed container even when > appl

[jira] [Updated] (YARN-6314) Potential infinite redirection on YARN log redirection web service

[ https://issues.apache.org/jira/browse/YARN-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6314: - Fix Version/s: 3.0.0-alpha3 > Potential infinite redirection on YARN log redirection web service >

[jira] [Commented] (YARN-6336) Jenkins report YARN new UI build failure

[ https://issues.apache.org/jira/browse/YARN-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924892#comment-15924892 ] Junping Du commented on YARN-6336: -- cc [~leftnoteasy], [~sunilg]. > Jenkins report YARN n

[jira] [Created] (YARN-6336) Jenkins report YARN new UI build failure

Junping Du created YARN-6336: Summary: Jenkins report YARN new UI build failure Key: YARN-6336 URL: https://issues.apache.org/jira/browse/YARN-6336 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is still running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924881#comment-15924881 ] Junping Du commented on YARN-6313: -- After checking from log, it seems build failure on UI

[jira] [Commented] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is still running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924734#comment-15924734 ] Junping Du commented on YARN-6313: -- I can build locally too. But Jenkins keep saying build

[jira] [Commented] (YARN-6314) Potential infinite redirection on YARN log redirection web service

[ https://issues.apache.org/jira/browse/YARN-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923384#comment-15923384 ] Junping Du commented on YARN-6314: -- +1. Committing it in. > Potential infinite redirectio

[jira] [Commented] (YARN-6314) Potential infinite redirection on YARN log redirection web service

[ https://issues.apache.org/jira/browse/YARN-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1592#comment-1592 ] Junping Du commented on YARN-6314: -- bq. So if NM address is provided by user in the beginn

[jira] [Commented] (YARN-6314) Potential infinite redirection on YARN log redirection web service

[ https://issues.apache.org/jira/browse/YARN-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922719#comment-15922719 ] Junping Du commented on YARN-6314: -- Thanks [~xgong] for reporting the issue and deliver a

[jira] [Updated] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is still running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6313: - Summary: yarn logs cli should provide logs for a completed container even when application is still running

[jira] [Updated] (YARN-6313) yarn logs cli should provide logs for a completed container even when application is running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6313: - Summary: yarn logs cli should provide logs for a completed container even when application is running (was

[jira] [Commented] (YARN-6313) yarn logs cli should provide logs for a completed container (with nm address provided) even when application is running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15915429#comment-15915429 ] Junping Du commented on YARN-6313: -- Update the title of this jira to reflect the improveme

[jira] [Updated] (YARN-6313) yarn logs cli should provide logs for a completed container (with nm address provided) even when application is running

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6313: - Summary: yarn logs cli should provide logs for a completed container (with nm address provided) even when a

[jira] [Commented] (YARN-6313) yarn logs cli does not provide logs for a completed container even when the nm address is provided

[ https://issues.apache.org/jira/browse/YARN-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15914204#comment-15914204 ] Junping Du commented on YARN-6313: -- This feature/improvement is very useful when we debugg

[jira] [Commented] (YARN-6143) Fix incompatible issue caused by YARN-3583

[ https://issues.apache.org/jira/browse/YARN-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906030#comment-15906030 ] Junping Du commented on YARN-6143: -- Looks like we forget to commit to branch-2.8.0. Commit

[jira] [Comment Edited] (YARN-5311) Document graceful decommission CLI and usage

[ https://issues.apache.org/jira/browse/YARN-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902101#comment-15902101 ] Junping Du edited comment on YARN-5311 at 3/8/17 10:41 PM: --- Sorry

[jira] [Commented] (YARN-5311) Document graceful decommission CLI and usage

[ https://issues.apache.org/jira/browse/YARN-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902101#comment-15902101 ] Junping Du commented on YARN-5311: -- Sorry for coming late on this as reviewing document is

[jira] [Updated] (YARN-5311) Document graceful decommission CLI and usage

[ https://issues.apache.org/jira/browse/YARN-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5311: - Labels: (was: oct16-easy) > Document graceful decommission CLI and usage > --

[jira] [Created] (YARN-6294) ATS client should better handle Socket closed case

Junping Du created YARN-6294: Summary: ATS client should better handle Socket closed case Key: YARN-6294 URL: https://issues.apache.org/jira/browse/YARN-6294 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-6271) yarn rmadin -getGroups returns information from standby RM

[ https://issues.apache.org/jira/browse/YARN-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895162#comment-15895162 ] Junping Du commented on YARN-6271: -- Two test failures are not related to patch and exists

[jira] [Commented] (YARN-6271) yarn rmadin -getGroups returns information from standby RM

[ https://issues.apache.org/jira/browse/YARN-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893450#comment-15893450 ] Junping Du commented on YARN-6271: -- Patch LGTM. +1 pending on Jenkins. > yarn rmadin -get

[jira] [Commented] (YARN-6265) yarn.resourcemanager.fail-fast is used inconsistently

[ https://issues.apache.org/jira/browse/YARN-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893101#comment-15893101 ] Junping Du commented on YARN-6265: -- Agree. IIRC, the later one - state store operation fai

[jira] [Commented] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888797#comment-15888797 ] Junping Du commented on YARN-6189: -- Thanks [~xgong] and [~templedf] for review! > Improve

[jira] [Commented] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883957#comment-15883957 ] Junping Du commented on YARN-6189: -- test failure should not be related. > Improve applica

[jira] [Commented] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883822#comment-15883822 ] Junping Du commented on YARN-6189: -- Thanks [~templedf] for review. v2 patch should incorpo

[jira] [Updated] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6189: - Attachment: YARN-6189-v2.patch > Improve application status log message when RM restarted when app is in NE

[jira] [Updated] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6189: - Attachment: YARN-6189.patch Thanks [~yeshavora] for reporting the issue. I agree that the message here cou

[jira] [Assigned] (YARN-6189) Improve application status log message when RM restarted when app is in NEW state

[ https://issues.apache.org/jira/browse/YARN-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-6189: Assignee: Junping Du > Improve application status log message when RM restarted when app is in NEW

[jira] [Commented] (YARN-6143) Fix incompatible issue caused by YARN-3583

[ https://issues.apache.org/jira/browse/YARN-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881618#comment-15881618 ] Junping Du commented on YARN-6143: -- Thanks [~leftnoteasy] and [~sunilg] for working on it.

[jira] [Commented] (YARN-5311) Document graceful decommission CLI and usage

[ https://issues.apache.org/jira/browse/YARN-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874876#comment-15874876 ] Junping Du commented on YARN-5311: -- Thanks [~elek] for updating the patch. I will review i

[jira] [Commented] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868851#comment-15868851 ] Junping Du commented on YARN-5068: -- bq. Since this JIRA is committed to 2.8 as well, rever

[jira] [Updated] (YARN-6174) Log files pattern should be same for both running and finished container

[ https://issues.apache.org/jira/browse/YARN-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6174: - Fix Version/s: 3.0.0-alpha3 > Log files pattern should be same for both running and finished container > --

[jira] [Commented] (YARN-6174) Log files pattern should be same for both running and finished container

[ https://issues.apache.org/jira/browse/YARN-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865970#comment-15865970 ] Junping Du commented on YARN-6174: -- The test failure is not related and get tracked in YAR

[jira] [Commented] (YARN-6174) Log files pattern should be same for both running and finished container

[ https://issues.apache.org/jira/browse/YARN-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864891#comment-15864891 ] Junping Du commented on YARN-6174: -- Yes. That's what I suggested offline. May be we can ad

[jira] [Commented] (YARN-6143) Fix incompatible issue caused by YARN-3583

[ https://issues.apache.org/jira/browse/YARN-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862286#comment-15862286 ] Junping Du commented on YARN-6143: -- Thanks [~leftnoteasy] for reporting this issue. Sounds

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861247#comment-15861247 ] Junping Du commented on YARN-6113: -- Sure. +1 on latest patch. Will commit it tomorrow if n

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859421#comment-15859421 ] Junping Du commented on YARN-6113: -- Thanks Xuan for updating the patch. Latest patch LGTM.

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857957#comment-15857957 ] Junping Du commented on YARN-6113: -- Patch looks good in over all. Just a minor one, logic

[jira] [Updated] (YARN-6145) Improve log message on fail over

[ https://issues.apache.org/jira/browse/YARN-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6145: - Fix Version/s: 3.0.0-alpha3 > Improve log message on fail over > > >

[jira] [Commented] (YARN-6145) Improve log message on fail over

[ https://issues.apache.org/jira/browse/YARN-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857048#comment-15857048 ] Junping Du commented on YARN-6145: -- Patch looks reasonable. Previous warn message for conn

[jira] [Commented] (YARN-6113) re-direct NM Web Service to get container logs for finished applications

[ https://issues.apache.org/jira/browse/YARN-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855705#comment-15855705 ] Junping Du commented on YARN-6113: -- YARN-6108 get committed, patch here should be ready fo

[jira] [Commented] (YARN-6108) Improve AHS webservice to accept NM address as a parameter to get container logs

[ https://issues.apache.org/jira/browse/YARN-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854020#comment-15854020 ] Junping Du commented on YARN-6108: -- Thanks [~xgong] for updating the patch. Sound like all

[jira] [Commented] (YARN-6108) Improve AHS webservice to accept NM address as a parameter to get container logs

[ https://issues.apache.org/jira/browse/YARN-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849870#comment-15849870 ] Junping Du commented on YARN-6108: -- Thanks [~xgong] for addressing my above comments. Quic

[jira] [Commented] (YARN-6108) Improve AHS webservice to accept NM address as a parameter to get container logs

[ https://issues.apache.org/jira/browse/YARN-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849677#comment-15849677 ] Junping Du commented on YARN-6108: -- YARN-6100 is committed, submit patch for this JIRA. >

[jira] [Updated] (YARN-6099) Improve webservice to list aggregated log files

[ https://issues.apache.org/jira/browse/YARN-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6099: - Fix Version/s: (was: 3.0.0-alpha2) 3.0.0-alpha3 > Improve webservice to list aggrega

[jira] [Updated] (YARN-6100) improve YARN webservice to output aggregated container logs

[ https://issues.apache.org/jira/browse/YARN-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6100: - Fix Version/s: 3.0.0-alpha3 > improve YARN webservice to output aggregated container logs > ---

[jira] [Assigned] (YARN-6049) Graceful Decommission web link is broken, gives 404 Not Found

[ https://issues.apache.org/jira/browse/YARN-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-6049: Assignee: Elek, Marton Hi [~elek], I just added you to yarn contributor and assigned this JIRA to yo

[jira] [Commented] (YARN-6100) improve YARN webservice to output aggregated container logs

[ https://issues.apache.org/jira/browse/YARN-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848004#comment-15848004 ] Junping Du commented on YARN-6100: -- Thanks [~xgong] for updating the patch! bq. Yes, we ha

[jira] [Commented] (YARN-6108) Improve AHS webservice to accept NM address as a parameter to get container logs

[ https://issues.apache.org/jira/browse/YARN-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847951#comment-15847951 ] Junping Du commented on YARN-6108: -- Thanks [~xgong] for working on this. A quick comment h

[jira] [Commented] (YARN-6126) Obtaining app logs for Running application fails with "Unable to parse json from webservice. Error:"

[ https://issues.apache.org/jira/browse/YARN-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842383#comment-15842383 ] Junping Du commented on YARN-6126: -- Sorry for missing this part in reviewing YARN-6099. Th

[jira] [Commented] (YARN-6099) Improve webservice to list aggregated log files

[ https://issues.apache.org/jira/browse/YARN-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834481#comment-15834481 ] Junping Du commented on YARN-6099: -- Thanks [~xgong] for updating the patch. The test failu

[jira] [Commented] (YARN-6099) Improve webservice to list aggregated log files

[ https://issues.apache.org/jira/browse/YARN-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832265#comment-15832265 ] Junping Du commented on YARN-6099: -- Thanks [~xgong] for this code refactor effort. The cod

[jira] [Updated] (YARN-4785) inconsistent value type of the "type" field for LeafQueueInfo in response of RM REST API - cluster/scheduler

[ https://issues.apache.org/jira/browse/YARN-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4785: - Release Note: Fix inconsistent value type ( String and Array ) of the "type" field for LeafQueueInfo in res

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4087: - Release Note: Set YARN_FAIL_FAST to be false by default. If HA is enabled and if there's any state-store er

[jira] [Updated] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2336: - Release Note: Fix FairScheduler's REST api returns a missing '[' blacket JSON for childQueues. > Fair sche

[jira] [Commented] (YARN-6011) Add a new web service to list the files on a container in AHSWebService

[ https://issues.apache.org/jira/browse/YARN-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824361#comment-15824361 ] Junping Du commented on YARN-6011: -- +1. > Add a new web service to list the files on a co

[jira] [Commented] (YARN-6011) Add a new web service to list the files on a container in AHSWebService

[ https://issues.apache.org/jira/browse/YARN-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822419#comment-15822419 ] Junping Du commented on YARN-6011: -- Latest patch LGTM. However, [~xgong], can you check if

[jira] [Commented] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822284#comment-15822284 ] Junping Du commented on YARN-6091: -- move to 2.8.1 given 2.8 is in RC process. > the AppMa

[jira] [Updated] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6091: - Target Version/s: 2.8.1 (was: 2.8.0) > the AppMaster register failed when use Docker on LinuxContainer >

[jira] [Updated] (YARN-6091) the AppMaster register failed when use Docker on LinuxContainer

[ https://issues.apache.org/jira/browse/YARN-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6091: - Fix Version/s: (was: 2.8.0) > the AppMaster register failed when use Docker on LinuxContainer > --

[jira] [Commented] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819036#comment-15819036 ] Junping Du commented on YARN-6072: -- I believe latest patch already incorporate Jian's comm

[jira] [Commented] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817277#comment-15817277 ] Junping Du commented on YARN-6072: -- Latest patch LGTM too. Thanks [~ajithshetty] for quick

[jira] [Resolved] (YARN-6079) simple spelling errors in yarn test code

[ https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-6079. -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.0.0-alpha2 2.9.0

[jira] [Commented] (YARN-6079) simple spelling errors in yarn test code

[ https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816900#comment-15816900 ] Junping Du commented on YARN-6079: -- I have commit the patch to trunk and branch-2. Thanks

[jira] [Commented] (YARN-6079) simple spelling errors in yarn test code

[ https://issues.apache.org/jira/browse/YARN-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816878#comment-15816878 ] Junping Du commented on YARN-6079: -- +1. Committing it in. > simple spelling errors in yar

[jira] [Updated] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4148: - Fix Version/s: 2.8.0 > When killing app, RM releases app's resource before they are released by NM > --

[jira] [Commented] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816837#comment-15816837 ] Junping Du commented on YARN-4148: -- The test failures should be unrelated to the patch. Te

[jira] [Commented] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped

[ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816484#comment-15816484 ] Junping Du commented on YARN-5416: -- Sorry for missing above comments, [~ebadger] and [~jlo

[jira] [Updated] (YARN-5416) TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently due to not wait SchedulerApplicationAttempt to be stopped

[ https://issues.apache.org/jira/browse/YARN-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5416: - Attachment: YARN-5416-v2.patch > TestRMRestart#testRMRestartWaitForPreviousAMToFinish failed intermittently

[jira] [Commented] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816360#comment-15816360 ] Junping Du commented on YARN-4148: -- Thanks Jason. I reopen the ticket for kicking off the

[jira] [Reopened] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened YARN-4148: -- > When killing app, RM releases app's resource before they are released by NM > -

[jira] [Commented] (YARN-6072) RM unable to start in secure mode

[ https://issues.apache.org/jira/browse/YARN-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816191#comment-15816191 ] Junping Du commented on YARN-6072: -- bq. // Set HA configuration should be done before logi

<    1   2   3   4   5   6   7   8   9   10   >