[jira] [Commented] (YARN-4709) NMWebServices produces incorrect JSON for containers

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158444#comment-15158444 ] Hudson commented on YARN-4709: -- FAILURE: Integrated in Hadoop-trunk-Commit #9345 (See [https:

[jira] [Updated] (YARN-4709) NMWebServices produces incorrect JSON for containers

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4709: Summary: NMWebServices produces incorrect JSON for containers (was: NMWebServices produce incorrect

[jira] [Updated] (YARN-4709) NMWebServices produce incorrect JSON for containers

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4709: Summary: NMWebServices produce incorrect JSON for containers (was: Exception when option to fetch al

[jira] [Commented] (YARN-4715) Add support to read resource types from a config file

[ https://issues.apache.org/jira/browse/YARN-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158293#comment-15158293 ] Varun Vasudev commented on YARN-4715: - Test failures are unrelated to the patch. > Add

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158237#comment-15158237 ] Sunil G commented on YARN-4634: --- Yes [~leftnoteasy], Thanks for pointing out this case. I th

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158230#comment-15158230 ] Sunil G commented on YARN-4712: --- Thanks Varun. Yes, such metrics has to be in double. > CPU

[jira] [Commented] (YARN-4694) Document ATS v1.5

[ https://issues.apache.org/jira/browse/YARN-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158219#comment-15158219 ] Li Lu commented on YARN-4694: - Hi [~xgong], have you started on this JIRA? If not can I take it

[jira] [Updated] (YARN-1310) Get rid of MR settings in YARN configuration

[ https://issues.apache.org/jira/browse/YARN-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-1310: --- Assignee: (was: Brahma Reddy Battula) > Get rid of MR settings in YARN configuratio

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158155#comment-15158155 ] Hadoop QA commented on YARN-4701: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158146#comment-15158146 ] Li Lu commented on YARN-4705: - Seems we need to somewhat handle this? This will happen when a s

[jira] [Created] (YARN-4720) Skip unnecessary NN operations in log aggregation

Ming Ma created YARN-4720: - Summary: Skip unnecessary NN operations in log aggregation Key: YARN-4720 URL: https://issues.apache.org/jira/browse/YARN-4720 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.003.patch > When task logs are not available, port 8041 is referenced instead of port

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: (was: yarn4701.003.patch) > When task logs are not available, port 8041 is referenced inste

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.003.patch Fixed the test failures and check style warnings. The rest are unrelated. >

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158032#comment-15158032 ] Hadoop QA commented on YARN-4697: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157994#comment-15157994 ] Hadoop QA commented on YARN-4701: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

[ https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-4718: -- Attachment: YARN-4718-v001.patch Left external webapp side as it was. Cleaning up {{SchedulerNode}}: gene

[jira] [Commented] (YARN-4484) Available Resource calculation for a queue is not correct when used with labels

[ https://issues.apache.org/jira/browse/YARN-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157919#comment-15157919 ] Wangda Tan commented on YARN-4484: -- Hi [~sunilg], Did you notice my [comment|https://iss

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157914#comment-15157914 ] Robert Kanter commented on YARN-4697: - Looks good overall. A few minor things: - Add a

[jira] [Commented] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

[ https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157873#comment-15157873 ] Karthik Kambatla commented on YARN-4718: The webapp changes are user-facing, don't

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157870#comment-15157870 ] Robert Kanter commented on YARN-4701: - LGTM. Not sure why Jenkins didn't run for this.

[jira] [Updated] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

[ https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-4718: -- Attachment: YARN-4718-v000.patch Done 1 and 2 from [~kasha] proposal (I may have gone a little crazy with

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157837#comment-15157837 ] Li Lu commented on YARN-4716: - bq. for the FS it propagates the flush down to the stream writin

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157822#comment-15157822 ] Steve Loughran commented on YARN-4716: -- For a flush I want them to be propagated to AT

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157771#comment-15157771 ] Wangda Tan commented on YARN-4634: -- [~sunilg], Thanks for explanations. Does this handle f

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157760#comment-15157760 ] Li Lu commented on YARN-4716: - +1, this is necessary to publish important lifecycle events for

[jira] [Commented] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157643#comment-15157643 ] Hadoop QA commented on YARN-4680: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157546#comment-15157546 ] Xuan Gong commented on YARN-4680: - Thanks, [~djp] and [~ste...@apache.org] for the review.

[jira] [Updated] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4680: Attachment: YARN-4680.20160222.patch > TimerTasks leak in ATS V1.5 Writer > -

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157482#comment-15157482 ] Bikas Saha commented on YARN-1011: -- 2.3 The relationship between overall cluster utilizati

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157474#comment-15157474 ] Hadoop QA commented on YARN-4696: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4715) Add support to read resource types from a config file

[ https://issues.apache.org/jira/browse/YARN-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157443#comment-15157443 ] Hadoop QA commented on YARN-4715: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-1488) Allow containers to delegate resources to another container

[ https://issues.apache.org/jira/browse/YARN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157425#comment-15157425 ] Arun Suresh commented on YARN-1488: --- [~acmurthy], [~vinodkv].. Wondering what the status

[jira] [Commented] (YARN-4690) Skip object allocation in FSAppAttempt#getResourceUsage when possible

[ https://issues.apache.org/jira/browse/YARN-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157397#comment-15157397 ] Ming Ma commented on YARN-4690: --- Thanks [~sjlee0] and [~kasha]! > Skip object allocation in

[jira] [Commented] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157389#comment-15157389 ] Junping Du commented on YARN-4680: -- Forget to mention, System.currentTimeMillis() should b

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-006.patch Patch 006; ongoing (and currently unsuccessful) attempt to use file

[jira] [Commented] (YARN-4680) TimerTasks leak in ATS V1.5 Writer

[ https://issues.apache.org/jira/browse/YARN-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157372#comment-15157372 ] Junping Du commented on YARN-4680: -- Patch LGTM too. Agree with [~ste...@apache.org] that w

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157273#comment-15157273 ] Jason Lowe commented on YARN-4705: -- bq. adding a check to skip 0-byte files stops the stac

[jira] [Commented] (YARN-4705) ATS 1.5 parse pipeline to consider handling open() events recoverably

[ https://issues.apache.org/jira/browse/YARN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157262#comment-15157262 ] Jason Lowe commented on YARN-4705: -- ATS 1.5 relies on reading files that are actively bein

[jira] [Commented] (YARN-4511) Create common scheduling policy for resource over-subscription

[ https://issues.apache.org/jira/browse/YARN-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157257#comment-15157257 ] Karthik Kambatla commented on YARN-4511: As discussed on YARN-1011, things we might

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157253#comment-15157253 ] Karthik Kambatla commented on YARN-1011: [~elgoiri] - for work that we want to get

[jira] [Created] (YARN-4719) Add a helper library to maintain node state and allows common queries

Karthik Kambatla created YARN-4719: -- Summary: Add a helper library to maintain node state and allows common queries Key: YARN-4719 URL: https://issues.apache.org/jira/browse/YARN-4719 Project: Hadoop

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157248#comment-15157248 ] Karthik Kambatla commented on YARN-1011: bq. Could you clarify 2.2? What would trig

[jira] [Commented] (YARN-4386) refreshNodesGracefully() should send recommission event to active RMNodes only

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157242#comment-15157242 ] Kuhu Shukla commented on YARN-4386: --- Thank you Junping for the review and commit! > ref

[jira] [Commented] (YARN-4386) refreshNodesGracefully() should send recommission event to active RMNodes only

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157239#comment-15157239 ] Junping Du commented on YARN-4386: -- Mark issue as resolved should be good enough for now.

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157240#comment-15157240 ] Brook Zhou commented on YARN-4677: -- Hi [~djp], I currently have no plan, would appreciate

[jira] [Commented] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157237#comment-15157237 ] Brook Zhou commented on YARN-3223: -- Thanks [~djp] for the kind reviews and followups. > R

[jira] [Commented] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

[ https://issues.apache.org/jira/browse/YARN-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157233#comment-15157233 ] Karthik Kambatla commented on YARN-4718: I was thinking of the following variable r

[jira] [Created] (YARN-4718) Rename variables in SchedulerNode to reduce ambiguity post YARN-1011

Karthik Kambatla created YARN-4718: -- Summary: Rename variables in SchedulerNode to reduce ambiguity post YARN-1011 Key: YARN-4718 URL: https://issues.apache.org/jira/browse/YARN-4718 Project: Hadoop

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157187#comment-15157187 ] Steve Loughran commented on YARN-4696: -- the next patch I put up will implement YARN-47

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157207#comment-15157207 ] Steve Loughran commented on YARN-4696: -- filed HADOOP-12831. I know I could avoid suffe

[jira] [Updated] (YARN-4709) Exception when option to fetch all log files is specified while using yarn logs -am command and incorrect JSON produced for containerLogFiles

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4709: Priority: Critical (was: Major) > Exception when option to fetch all log files is specified while us

[jira] [Commented] (YARN-4709) Exception when option to fetch all log files is specified while using yarn logs -am command and incorrect JSON produced for containerLogFiles

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157135#comment-15157135 ] Varun Vasudev commented on YARN-4709: - +1 for the fix. My apologies for missing this. I

[jira] [Commented] (YARN-4386) refreshNodesGracefully() looks at active RMNode list for recommissioning decommissioned nodes

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157022#comment-15157022 ] Junping Du commented on YARN-4386: -- v2 patch LGTM. +1. Will commit it shortly. > refreshN

[jira] [Commented] (YARN-4386) refreshNodesGracefully() should send recommission event to active RMNodes only

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157109#comment-15157109 ] Kuhu Shukla commented on YARN-4386: --- Thanks a lot Junping. Can we close the JIRA as resol

[jira] [Commented] (YARN-4386) refreshNodesGracefully() should send recommission event to active RMNodes only

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157101#comment-15157101 ] Hudson commented on YARN-4386: -- FAILURE: Integrated in Hadoop-trunk-Commit #9340 (See [https:

[jira] [Created] (YARN-4717) TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup

Daniel Templeton created YARN-4717: -- Summary: TestResourceLocalizationService.testPublicResourceInitializesLocalDir fails Intermittently due to IllegalArgumentException from cleanup Key: YARN-4717 URL: https://i

[jira] [Updated] (YARN-4386) refreshNodesGracefully() should send recommission event to active RMNodes only

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4386: - Summary: refreshNodesGracefully() should send recommission event to active RMNodes only (was: refreshNodes

[jira] [Commented] (YARN-4711) NPE in NMTimelinePublisher

[ https://issues.apache.org/jira/browse/YARN-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157069#comment-15157069 ] Naganarasimha G R commented on YARN-4711: - Seems like this is caused due to YARN-33

[jira] [Updated] (YARN-4715) Add support to read resource types from a config file

[ https://issues.apache.org/jira/browse/YARN-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4715: Attachment: YARN-4715-YARN-3926.002.patch Uploaded a new patch with fixes for checkstyle, findbugs an

[jira] [Commented] (YARN-4671) There is no need to acquire CS lock when completing a container

[ https://issues.apache.org/jira/browse/YARN-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156932#comment-15156932 ] Jian He commented on YARN-4671: --- +1, lgtm > There is no need to acquire CS lock when complet

[jira] [Commented] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156929#comment-15156929 ] Junping Du commented on YARN-4716: -- +1 to add a flush() API to TimelineClient especially w

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156923#comment-15156923 ] Junping Du commented on YARN-4677: -- Thanks [~brookz] for filing this ticket to address my

[jira] [Commented] (YARN-4709) Exception when option to fetch all log files is specified while using yarn logs -am command and incorrect JSON produced for containerLogFiles

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156842#comment-15156842 ] Hadoop QA commented on YARN-4709: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote |

[jira] [Commented] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156894#comment-15156894 ] Junping Du commented on YARN-3223: -- Thanks [~brookz] for updating the patch. With a TODO i

[jira] [Updated] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3223: - Target Version/s: 2.8.0 (was: 2.7.1) > Resource update during NM graceful decommission > -

[jira] [Commented] (YARN-4715) Add support to read resource types from a config file

[ https://issues.apache.org/jira/browse/YARN-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156847#comment-15156847 ] Hadoop QA commented on YARN-4715: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

[ https://issues.apache.org/jira/browse/YARN-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4716: - Target Version/s: 2.8.0 > TimelineClient to implement Flushable; propagate to writer >

[jira] [Created] (YARN-4716) TimelineClient to implement Flushable; propagate to writer

Steve Loughran created YARN-4716: Summary: TimelineClient to implement Flushable; propagate to writer Key: YARN-4716 URL: https://issues.apache.org/jira/browse/YARN-4716 Project: Hadoop YARN

[jira] [Commented] (YARN-4709) Exception when option to fetch all log files is specified while using yarn logs -am command and incorrect JSON produced for containerLogFiles

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156831#comment-15156831 ] Hadoop QA commented on YARN-4709: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote |

[jira] [Created] (YARN-4715) Add support to read resource types from a config file

Varun Vasudev created YARN-4715: --- Summary: Add support to read resource types from a config file Key: YARN-4715 URL: https://issues.apache.org/jira/browse/YARN-4715 Project: Hadoop YARN Issue T

[jira] [Updated] (YARN-4715) Add support to read resource types from a config file

[ https://issues.apache.org/jira/browse/YARN-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4715: Attachment: YARN-4715-YARN-3926.001.patch > Add support to read resource types from a config file > -

[jira] [Updated] (YARN-4709) Exception when option to fetch all log files is specified while using yarn logs -am command and incorrect JSON produced for containerLogFiles

[ https://issues.apache.org/jira/browse/YARN-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4709: --- Attachment: YARN-4709.02.patch > Exception when option to fetch all log files is specified while using

[jira] [Commented] (YARN-4328) Findbugs warning in resourcemanager in branch-2.7 and branch-2.6

[ https://issues.apache.org/jira/browse/YARN-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156761#comment-15156761 ] Hadoop QA commented on YARN-4328: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4714) [Java 8] Over usage of virtual memory

[ https://issues.apache.org/jira/browse/YARN-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156759#comment-15156759 ] Steve Loughran commented on YARN-4714: -- true, but it's still traumatic: cluster perfor

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156642#comment-15156642 ] Varun Saxena commented on YARN-4712: I dont thnk its related to YARN-4308. This is rela

[jira] [Commented] (YARN-4714) [Java 8] Over usage of virtual memory

[ https://issues.apache.org/jira/browse/YARN-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156620#comment-15156620 ] Akira AJISAKA commented on YARN-4714: - In YARN-2225, Tsuyoshi commented: bq. IMHO, I pr

[jira] [Moved] (YARN-4714) [Java 8] Over usage of virtual memory

[ https://issues.apache.org/jira/browse/YARN-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA moved HADOOP-11364 to YARN-4714: -- Key: YARN-4714 (was: HADOOP-11364) Project: Hadoop YARN (was: H

[jira] [Commented] (YARN-4707) Remove the extra char (>) from SecureContainer.md

[ https://issues.apache.org/jira/browse/YARN-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156617#comment-15156617 ] Brahma Reddy Battula commented on YARN-4707: [~ajisakaa] thanks a lot for revie

[jira] [Resolved] (YARN-2225) Turn the virtual memory check to be off by default

[ https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved YARN-2225. - Resolution: Won't Fix > Turn the virtual memory check to be off by default > --

[jira] [Commented] (YARN-2225) Turn the virtual memory check to be off by default

[ https://issues.apache.org/jira/browse/YARN-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156615#comment-15156615 ] Akira AJISAKA commented on YARN-2225: - bq. IMHO, I prefer to make the default value of

[jira] [Commented] (YARN-4707) Remove the extra char (>) from SecureContainer.md

[ https://issues.apache.org/jira/browse/YARN-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156614#comment-15156614 ] Hudson commented on YARN-4707: -- FAILURE: Integrated in Hadoop-trunk-Commit #9339 (See [https:

[jira] [Updated] (YARN-4707) Remove the extra char (>) from SecureContainer.md

[ https://issues.apache.org/jira/browse/YARN-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4707: Affects Version/s: 2.7.2 Summary: Remove the extra char (>) from SecureContainer.md (wa

[jira] [Commented] (YARN-4707) Remove the extra char (>) from the SecureContainer.md

[ https://issues.apache.org/jira/browse/YARN-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156604#comment-15156604 ] Akira AJISAKA commented on YARN-4707: - LGTM, +1. > Remove the extra char (>) from the