[jira] [Updated] (YARN-5581) [Atsv2] Reuse the API doc for a same funtionality methods in TimelineReaderWebServices class

[ https://issues.apache.org/jira/browse/YARN-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5581: Labels: maintenance (was: ) > [Atsv2] Reuse the API doc for a same funtionality methods in

[jira] [Created] (YARN-5581) [Atsv2] Reuse the API doc for a same funtionality methods in TimelineReaderWebServices class

Rohith Sharma K S created YARN-5581: --- Summary: [Atsv2] Reuse the API doc for a same funtionality methods in TimelineReaderWebServices class Key: YARN-5581 URL: https://issues.apache.org/jira/browse/YARN-5581

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no userId

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448041#comment-15448041 ] Rohith Sharma K S commented on YARN-4220: - Multiple application entity reader enforces to provide

[jira] [Updated] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated YARN-5550: Fix Version/s: 3.0.0-alpha2 2.8.0 > TestYarnCLI#testGetContainers should format according

[jira] [Commented] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448000#comment-15448000 ] Naganarasimha G R commented on YARN-5567: - Thanks for pointing it out [~wilfreds], but it was not

[jira] [Commented] (YARN-3671) Integrate Federation services with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447986#comment-15447986 ] Jian He commented on YARN-3671: --- Looks good, Committed to YARN-2915. Thanks Subru ! > Integrate Federation

[jira] [Commented] (YARN-5574) TestDistributedShell sets yarn.log.dir in the configuration instead of as a system property

[ https://issues.apache.org/jira/browse/YARN-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447882#comment-15447882 ] Tao Jie commented on YARN-5574: --- I don't see any difference when I set "yarn.log.dir" or not in this

[jira] [Reopened] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reopened YARN-5567: - The script handling had a lot of comments in it why the exit code was ignored and an

[jira] [Updated] (YARN-5552) Add Builder methods for common yarn API records

[ https://issues.apache.org/jira/browse/YARN-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5552: -- Assignee: Tao Jie > Add Builder methods for common yarn API records >

[jira] [Commented] (YARN-5552) Add Builder methods for common yarn API records

[ https://issues.apache.org/jira/browse/YARN-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447810#comment-15447810 ] Arun Suresh commented on YARN-5552: --- Sure [~Tao Jie].. Assigning this to you. Thanks !! > Add Builder

[jira] [Commented] (YARN-5552) Add Builder methods for common yarn API records

[ https://issues.apache.org/jira/browse/YARN-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447789#comment-15447789 ] Tao Jie commented on YARN-5552: --- Hi [~asuresh], I would like to take this Jira over, if you have not started

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447776#comment-15447776 ] Rohith Sharma K S commented on YARN-5561: - bq. Currently not supported. What's the use case for

[jira] [Commented] (YARN-3671) Integrate Federation services with ResourceManager

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

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

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

[jira] [Updated] (YARN-5543) ResourceManager SchedulingMonitor could potentially terminate the preemption checker thread

[ https://issues.apache.org/jira/browse/YARN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Shen updated YARN-5543: --- Attachment: YARN-5543.003.patch > ResourceManager SchedulingMonitor could potentially terminate the preemption

[jira] [Commented] (YARN-5526) DrainDispacher#ServiceStop blocked if setDrainEventsOnStop invoked

[ https://issues.apache.org/jira/browse/YARN-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447542#comment-15447542 ] Andrew Wang commented on YARN-5526: --- FYI for future git log greppers, this one was minorly typo'd as

[jira] [Commented] (YARN-5337) Dshell AM failed with "java.lang.OutOfMemoryError: GC overhead limit exceeded"

[ https://issues.apache.org/jira/browse/YARN-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447539#comment-15447539 ] Andrew Wang commented on YARN-5337: --- Tracked this one down in git log, here's the commit: {quote} commit

[jira] [Commented] (YARN-5002) getApplicationReport call may raise NPE for removed queues

[ https://issues.apache.org/jira/browse/YARN-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447535#comment-15447535 ] Andrew Wang commented on YARN-5002: --- FYI for git log greppers, this one is missing the JIRA ID in commit

[jira] [Commented] (YARN-4955) Add retry for SocketTimeoutException in TimelineClient

[ https://issues.apache.org/jira/browse/YARN-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447532#comment-15447532 ] Andrew Wang commented on YARN-4955: --- FYI for git log greppers that this one is missing commit message,

[jira] [Commented] (YARN-4815) ATS 1.5 timelineclient impl try to create attempt directory for every event call

[ https://issues.apache.org/jira/browse/YARN-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447527#comment-15447527 ] Andrew Wang commented on YARN-4815: --- FYI for git log greppers, this JIRA # was typo'd as YARN-4814 (with

[jira] [Commented] (YARN-4749) Generalize config file handling in container-executor

[ https://issues.apache.org/jira/browse/YARN-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447520#comment-15447520 ] Andrew Wang commented on YARN-4749: --- FYI for future git log greppers, the JIRA # was typo'd as YARN-4245.

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

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

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

[ https://issues.apache.org/jira/browse/YARN-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447516#comment-15447516 ] Andrew Wang commented on YARN-4717: --- FYI for future git log greppers, this one is missing the JIRA #. >

[jira] [Resolved] (YARN-4072) ApplicationHistoryServer, WebAppProxyServer, NodeManager and ResourceManager to support JvmPauseMonitor as a service

[ https://issues.apache.org/jira/browse/YARN-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved YARN-4072. --- Resolution: Duplicate Fix Version/s: (was: 2.9.0) > ApplicationHistoryServer,

[jira] [Reopened] (YARN-4072) ApplicationHistoryServer, WebAppProxyServer, NodeManager and ResourceManager to support JvmPauseMonitor as a service

[ https://issues.apache.org/jira/browse/YARN-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened YARN-4072: --- > ApplicationHistoryServer, WebAppProxyServer, NodeManager and ResourceManager > to support

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447509#comment-15447509 ] Andrew Wang commented on YARN-3225: --- FYI for git log greppers that the JIRA ID is missing in the commit

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

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

[jira] [Commented] (YARN-4734) Merge branch:YARN-3368 to trunk

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

[jira] [Commented] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447465#comment-15447465 ] Yufei Gu commented on YARN-5567: Thanks [~rchiang] for the review and commit! Thanks [~Naganarasimha] for

[jira] [Commented] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447442#comment-15447442 ] Hudson commented on YARN-5567: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10371 (See

[jira] [Commented] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447399#comment-15447399 ] Jonathan Hung commented on YARN-5550: - Awesome, thanks [~zhz]! > TestYarnCLI#testGetContainers should

[jira] [Commented] (YARN-3671) Integrate Federation services with ResourceManager

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

[jira] [Comment Edited] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447381#comment-15447381 ] Arun Suresh edited comment on YARN-5221 at 8/29/16 11:21 PM: - Hmmm... not sure

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447381#comment-15447381 ] Arun Suresh commented on YARN-5221: --- Hmmm... not sure if you r looking at the correct version of the

[jira] [Updated] (YARN-3671) Integrate Federation services with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3671: - Attachment: YARN-3671-YARN-2915-v5.patch Fixing the checkstyle warning that can be addressed (v5).

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447362#comment-15447362 ] Wangda Tan commented on YARN-5221: -- [~asuresh], Not only setVersion :(, there're more unaddressed

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447353#comment-15447353 ] Arun Suresh commented on YARN-5221: --- bq. ... could you double check my previous comment and let me know

[jira] [Updated] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5221: -- Attachment: YARN-5221.012.patch Aah... missed the {{Container::setVersion}} comment... Uploading patch

[jira] [Updated] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5567: - Summary: Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus (was:

[jira] [Commented] (YARN-3671) Integrate Federation services with ResourceManager

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

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447323#comment-15447323 ] Wangda Tan commented on YARN-5221: -- [~asuresh], bq. So new NM will be able to read old data.. but not the

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447317#comment-15447317 ] Arun Suresh commented on YARN-5221: --- Also raised YARN-5580 to track [~subru]'s suggestion.. > Expose

[jira] [Updated] (YARN-5579) Resourcemanager should surface failed state store operation prominently

[ https://issues.apache.org/jira/browse/YARN-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-5579: - Affects Version/s: 2.7.3 > Resourcemanager should surface failed state store operation prominently >

[jira] [Created] (YARN-5580) Refactor Scheduler to take only an single list of container updates

Arun Suresh created YARN-5580: - Summary: Refactor Scheduler to take only an single list of container updates Key: YARN-5580 URL: https://issues.apache.org/jira/browse/YARN-5580 Project: Hadoop YARN

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447310#comment-15447310 ] Daniel Templeton commented on YARN-5549: Sounds like we're agreed that we should go with patch 3.

[jira] [Updated] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4767: --- Attachment: YARN-4767.010.patch > Network issues can cause persistent RM UI outage >

[jira] [Updated] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5221: -- Attachment: YARN-5221.011.patch Updating patch based on [~subru]'s and [~leftnoteasy]'s suggestions.

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

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

[jira] [Commented] (YARN-5567) NodeHealthScriptRunner#reportHealthStatus bug fix

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447283#comment-15447283 ] Ray Chiang commented on YARN-5567: -- +1 for me as well. Will commit this soon. >

[jira] [Created] (YARN-5579) Resourcemanager should surface failed state store operation prominently

Ted Yu created YARN-5579: Summary: Resourcemanager should surface failed state store operation prominently Key: YARN-5579 URL: https://issues.apache.org/jira/browse/YARN-5579 Project: Hadoop YARN

[jira] [Commented] (YARN-5543) ResourceManager SchedulingMonitor could potentially terminate the preemption checker thread

[ https://issues.apache.org/jira/browse/YARN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447280#comment-15447280 ] Wangda Tan commented on YARN-5543: -- Thanks [~mshen], Mind to update this checkstyle report? -

[jira] [Updated] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4767: --- Attachment: (was: YARN-4767.010.patch) > Network issues can cause persistent RM UI outage

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447251#comment-15447251 ] Jason Lowe commented on YARN-5549: -- Totally agree with Daniel that this is only useful for debugging a

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447238#comment-15447238 ] Vinod Kumar Vavilapalli commented on YARN-5549: --- bq. Enabling the log message will require a

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

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

[jira] [Commented] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447185#comment-15447185 ] Hudson commented on YARN-5550: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10369 (See

[jira] [Commented] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

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

[jira] [Updated] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated YARN-5550: Hadoop Flags: Reviewed Fix Version/s: 2.7.4 Component/s: test client Thanks

[jira] [Comment Edited] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447168#comment-15447168 ] Wangda Tan edited comment on YARN-5221 at 8/29/16 9:54 PM: --- [~asuresh], Sorry

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447168#comment-15447168 ] Wangda Tan commented on YARN-5221: -- [~asuresh], Sorry for my late comment, some minor issues for

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447158#comment-15447158 ] Daniel Templeton commented on YARN-5549: With the log message set to debug and guarded by a

[jira] [Updated] (YARN-3671) Integrate Federation services with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3671: - Attachment: YARN-3671-YARN-2915-v4.patch bq. Here, the scheduler is passed in via reference. If

[jira] [Commented] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447096#comment-15447096 ] Jonathan Hung commented on YARN-5550: - Thanks [~zhz] for the review! Attached patch. >

[jira] [Updated] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-5550: Attachment: YARN-5550.003.patch > TestYarnCLI#testGetContainers should format according to

[jira] [Commented] (YARN-5543) ResourceManager SchedulingMonitor could potentially terminate the preemption checker thread

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

[jira] [Updated] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4767: --- Attachment: YARN-4767.010.patch Here's a patch that fixes the test failure. > Network issues

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447070#comment-15447070 ] Ray Chiang commented on YARN-5549: -- [~Naganarasimha], so you'd rather stick to version 003 of the patch?

[jira] [Comment Edited] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447057#comment-15447057 ] Daniel Templeton edited comment on YARN-4767 at 8/29/16 9:11 PM: - Oh,

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447057#comment-15447057 ] Daniel Templeton commented on YARN-4767: Oh, whoops. Missed the unit test failure. Huh. It

[jira] [Comment Edited] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447038#comment-15447038 ] Daniel Templeton edited comment on YARN-4767 at 8/29/16 9:07 PM: - This

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447051#comment-15447051 ] Daniel Templeton commented on YARN-4767: Actually, I am testing with the "cluster" prefix in

[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447053#comment-15447053 ] Vinod Kumar Vavilapalli commented on YARN-4767: --- Yes, then the tests should be fixed - they

[jira] [Comment Edited] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447038#comment-15447038 ] Daniel Templeton edited comment on YARN-4767 at 8/29/16 9:02 PM: - This

[jira] [Updated] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4767: --- Attachment: YARN-4767.009.patch This patches addresses the checkstyle issues. The javadoc

[jira] [Commented] (YARN-4734) Merge branch:YARN-3368 to trunk

[ https://issues.apache.org/jira/browse/YARN-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447006#comment-15447006 ] Hadoop QA commented on YARN-4734: - (!) A patch to the testing environment has been detected. Re-executing

[jira] [Commented] (YARN-5543) ResourceManager SchedulingMonitor could potentially terminate the preemption checker thread

[ https://issues.apache.org/jira/browse/YARN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446963#comment-15446963 ] Min Shen commented on YARN-5543: [~wangda], Revised patch attached. Could you please take a look? >

[jira] [Updated] (YARN-5543) ResourceManager SchedulingMonitor could potentially terminate the preemption checker thread

[ https://issues.apache.org/jira/browse/YARN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Min Shen updated YARN-5543: --- Attachment: YARN-5543.002.patch > ResourceManager SchedulingMonitor could potentially terminate the preemption

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446874#comment-15446874 ] Subru Krishnan commented on YARN-5221: -- Thanks [~asuresh] for addressing my feedback. I feel few of

[jira] [Commented] (YARN-5550) TestYarnCLI#testGetContainers should format according to CONTAINER_PATTERN

[ https://issues.apache.org/jira/browse/YARN-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446717#comment-15446717 ] Zhe Zhang commented on YARN-5550: - Thanks [~jhung] for taking on the work. Patch LGTM overall. A couple of

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446709#comment-15446709 ] Li Lu commented on YARN-5561: - Thanks! That's fine. Once we keep this behavior consistent we're good. >

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446698#comment-15446698 ] Varun Saxena commented on YARN-5561: bq. Is there a way to specify "unlimit" Not as such. Max value of

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446641#comment-15446641 ] Li Lu commented on YARN-5561: - Ah I just checked the v0 patch, the current approach to keep default limit to

[jira] [Updated] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5561: Issue Type: Sub-task (was: Bug) Parent: YARN-5355 > [Atsv2] : Support for ability to retrieve

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446573#comment-15446573 ] Varun Saxena commented on YARN-5561: bq. FromId is something which filter need to support so from where

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446553#comment-15446553 ] Li Lu commented on YARN-5561: - One potential problem of returning all apps in a cluster/containers in an app

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446476#comment-15446476 ] Rohith Sharma K S commented on YARN-5561: - Attached a patch for supporting legacy API i.e

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446467#comment-15446467 ] Rohith Sharma K S commented on YARN-5561: - It is required to get all the apps in cluster. REST

[jira] [Updated] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5561: Attachment: YARN-5561.v0.patch > [Atsv2] : Support for ability to retrieve

[jira] [Commented] (YARN-5560) Clean up bad exception catching practices in TestYarnClient

[ https://issues.apache.org/jira/browse/YARN-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446434#comment-15446434 ] Sean Po commented on YARN-5560: --- Thanks [~jlowe] for the review and committing! > Clean up bad exception

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446415#comment-15446415 ] Varun Saxena commented on YARN-5561: If merely list of apps within a cluster is required(without any

[jira] [Commented] (YARN-5570) NodeManager blocks kill attempts during startup if ResourceManager is down

[ https://issues.apache.org/jira/browse/YARN-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446394#comment-15446394 ] Allen Wittenauer commented on YARN-5570: That's going to be an interesting interaction with the

[jira] [Commented] (YARN-5560) Clean up bad exception catching practices in TestYarnClient

[ https://issues.apache.org/jira/browse/YARN-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446383#comment-15446383 ] Hudson commented on YARN-5560: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10365 (See

[jira] [Updated] (YARN-5570) NodeManager blocks kill attempts during startup if ResourceManager is down

[ https://issues.apache.org/jira/browse/YARN-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-5570: --- Affects Version/s: 2.7.2 > NodeManager blocks kill attempts during startup if ResourceManager

[jira] [Commented] (YARN-5570) NodeManager blocks kill attempts during startup if ResourceManager is down

[ https://issues.apache.org/jira/browse/YARN-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446370#comment-15446370 ] Daniel Templeton commented on YARN-5570: Yep, YARN-679 has an interrupt escalation mechanism, where

[jira] [Commented] (YARN-5561) [Atsv2] : Support for ability to retrieve apps/app-attempt/containers and entities via REST

[ https://issues.apache.org/jira/browse/YARN-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446353#comment-15446353 ] Varun Saxena commented on YARN-5561: Copying my comment over from YARN-5571. If we have to support

[jira] [Commented] (YARN-5560) Clean up bad exception catching practices in TestYarnClient

[ https://issues.apache.org/jira/browse/YARN-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446310#comment-15446310 ] Jason Lowe commented on YARN-5560: -- +1, committing this. > Clean up bad exception catching practices in

[jira] [Commented] (YARN-5571) [Atsv2] Query App REST endpoing need not to expose queryParams such userId/flowname/flowrunid

[ https://issues.apache.org/jira/browse/YARN-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445992#comment-15445992 ] Varun Saxena commented on YARN-5571: Ok... We can have discussion on REST endpoints on YARN-5561 and do

[jira] [Commented] (YARN-5577) [Atsv2] Document object passing in infofilters with an example

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

[jira] [Commented] (YARN-5571) [Atsv2] Query App REST endpoing need not to expose queryParams such userId/flowname/flowrunid

[ https://issues.apache.org/jira/browse/YARN-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445888#comment-15445888 ] Rohith Sharma K S commented on YARN-5571: - bq. support fetching all the apps within a cluster, upto

[jira] [Commented] (YARN-5571) [Atsv2] Query App REST endpoing need not to expose queryParams such userId/flowname/flowrunid

[ https://issues.apache.org/jira/browse/YARN-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15445869#comment-15445869 ] Varun Saxena commented on YARN-5571: If we have to support fetching all the apps within a cluster, upto

  1   2   >