[jira] [Resolved] (YARN-5038) [YARN-3368] Application and Container pages shows wrong values when RM is stopped

[ https://issues.apache.org/jira/browse/YARN-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-5038. --- Resolution: Duplicate YARN-4515 will handle this issue. > [YARN-3368] Application and Container pages shows

[jira] [Commented] (YARN-4738) Notify the RM about the status of OPPORTUNISTIC containers

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

[jira] [Commented] (YARN-4738) Notify the RM about the status of OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/YARN-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283429#comment-15283429 ] Arun Suresh commented on YARN-4738: --- [~kkaranasos], Thanks for the updated patch.. don't think this

[jira] [Commented] (YARN-5016) Add support for a minimum retry interval

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

[jira] [Updated] (YARN-5016) Add support for a minimum retry interval

[ https://issues.apache.org/jira/browse/YARN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-5016: --- Attachment: YARN-5016.01.patch Attach a patch to address it. > Add support for a minimum retry interval >

[jira] [Updated] (YARN-4738) Notify the RM about the status of OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/YARN-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-4738: - Attachment: YARN-4738.004.patch Fixing findbugs and uploading new version. >

[jira] [Commented] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

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

[jira] [Commented] (YARN-4738) Notify the RM about the status of OPPORTUNISTIC containers

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

[jira] [Updated] (YARN-4515) [YARN-3368] Support hosting web UI framework inside YARN RM

[ https://issues.apache.org/jira/browse/YARN-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4515: -- Attachment: YARN-4515-YARN-3368.6.patch Missed one comment from [~leftnoteasy] earlier. Node UI link will now

[jira] [Updated] (YARN-4515) [YARN-3368] Support hosting web UI framework inside YARN RM

[ https://issues.apache.org/jira/browse/YARN-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4515: -- Attachment: YARN-4515-YARN-3368.5.patch Thank you [~leftnoteasy] for the comments. - Fixed the finished time

[jira] [Updated] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-5082: --- Attachment: (was: YARN-5082.01.patch) > ContainerId rapidly increased in fair scheduler if the num of

[jira] [Updated] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-5082: --- Attachment: YARN-5082.01.patch > ContainerId rapidly increased in fair scheduler if the num of node app >

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

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

[jira] [Updated] (YARN-4738) Notify the RM about the status of OPPORTUNISTIC containers

[ https://issues.apache.org/jira/browse/YARN-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-4738: - Attachment: YARN-4738.003.patch Attaching new patch with some minor fixes. Test

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

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

[jira] [Commented] (YARN-5020) Fix Documentation for Yarn Capacity Scheduler on Resource Calculator

[ https://issues.apache.org/jira/browse/YARN-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283318#comment-15283318 ] Jo Desmet commented on YARN-5020: - Thanks after patch - reads as intended. > Fix Documentation for Yarn

[jira] [Updated] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-5082: --- Attachment: YARN-5082.01.patch > ContainerId rapidly increased in fair scheduler if the num of node app >

[jira] [Commented] (YARN-4097) Create POC timeline web UI with new YARN web UI framework

[ https://issues.apache.org/jira/browse/YARN-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283307#comment-15283307 ] Li Lu commented on YARN-4097: - I've rebased the POC patch to the latest YARN-3368 branch. While rebasing and

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

[ https://issues.apache.org/jira/browse/YARN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283272#comment-15283272 ] Jian He commented on YARN-1942: --- - setter should remain private/unstable {code} @Public @Stable

[jira] [Commented] (YARN-5006) ResourceManager quit due to ApplicationStateData exceed the limit size of znode in zk

[ https://issues.apache.org/jira/browse/YARN-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283261#comment-15283261 ] Tsuyoshi Ozawa commented on YARN-5006: -- {quote} Our opinion about fixing this bug is that we want to

[jira] [Commented] (YARN-4325) Purge app state from NM state-store should cover more LOG_HANDLING cases

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

[jira] [Updated] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4913: Attachment: YARN-4913.6.patch > Yarn logs should take a -out option to write to a directory >

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283204#comment-15283204 ] Xuan Gong commented on YARN-4913: - Thanks for the review. [~vvasudev] bq. Can you please change the help

[jira] [Updated] (YARN-4325) Purge app state from NM state-store should cover more LOG_HANDLING cases

[ https://issues.apache.org/jira/browse/YARN-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4325: - Attachment: YARN-4325-v4.patch Nice catch, [~jlowe]! v4 patch incorporate your comments and add a test to

[jira] [Updated] (YARN-1815) RM should record final state for unmanaged AMs

[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1815: -- Target Version/s: 2.8.1 (was: 2.8.0) The patch is still ways off per comments

[jira] [Updated] (YARN-2919) Potential race between renew and cancel in DelegationTokenRenwer

[ https://issues.apache.org/jira/browse/YARN-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2919: -- Target Version/s: 2.8.1 (was: 2.8.0) Cannot hold 2.8.0 for this forever. It's a

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

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

[jira] [Updated] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-4006: -- Target Version/s: 2.8.1 (was: 2.8.0) Cannot block 2.8.0 release for ever for

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283130#comment-15283130 ] Arun Suresh commented on YARN-2888: --- The testcase errors are not related to the patch.. There is no point

[jira] [Assigned] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-5087: - Assignee: Arun Suresh > Expose API to allow AM to request for change of container ExecutionType >

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

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

[jira] [Created] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

Arun Suresh created YARN-5087: - Summary: Expose API to allow AM to request for change of container ExecutionType Key: YARN-5087 URL: https://issues.apache.org/jira/browse/YARN-5087 Project: Hadoop YARN

[jira] [Resolved] (YARN-5086) Add support for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-5086. --- Resolution: Duplicate Closing as Duplicate of YARN-5085 > Add support for change of container

[jira] [Created] (YARN-5086) Add support for change of container ExecutionType

Arun Suresh created YARN-5086: - Summary: Add support for change of container ExecutionType Key: YARN-5086 URL: https://issues.apache.org/jira/browse/YARN-5086 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-5085) Add support for change of container ExecutionType

Arun Suresh created YARN-5085: - Summary: Add support for change of container ExecutionType Key: YARN-5085 URL: https://issues.apache.org/jira/browse/YARN-5085 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-5084) Cannot obtain AM container logs for the finished application using YARN CLI

Sumana Sathish created YARN-5084: Summary: Cannot obtain AM container logs for the finished application using YARN CLI Key: YARN-5084 URL: https://issues.apache.org/jira/browse/YARN-5084 Project:

[jira] [Created] (YARN-5083) YARN CLI for AM logs does not give any error message if entered invalid am value

Sumana Sathish created YARN-5083: Summary: YARN CLI for AM logs does not give any error message if entered invalid am value Key: YARN-5083 URL: https://issues.apache.org/jira/browse/YARN-5083

[jira] [Commented] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link

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

[jira] [Commented] (YARN-5006) ResourceManager quit due to ApplicationStateData exceed the limit size of znode in zk

[ https://issues.apache.org/jira/browse/YARN-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283009#comment-15283009 ] Daniel Templeton commented on YARN-5006: You should also see if YARN-4958 would help resolve the

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282987#comment-15282987 ] Karthik Kambatla commented on YARN-5079: I agree with Hitesh. The mailing list might be more

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282968#comment-15282968 ] Jonathan Maron commented on YARN-4757: -- We did take a look - I even POC'd an approach. We found some

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282962#comment-15282962 ] Jian He commented on YARN-4002: --- Yeah, I think so. because otherwise node heartbeat still competes on the

[jira] [Updated] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link

[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5041: - Attachment: yarn5041.002.patch Thanks for letting me know. The test failures were indeed caused by my

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282939#comment-15282939 ] Vinod Kumar Vavilapalli commented on YARN-5079: --- bq. Vinod Kumar Vavilapalli, there was a

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888.011.patch > Corrective mechanisms for rebalancing NM container queues >

[jira] [Resolved] (YARN-342) RM doesn't retry token renewals

[ https://issues.apache.org/jira/browse/YARN-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-342. -- Resolution: Not A Problem I think DFS client will do the retry automatically. Close this as this blocks 2.8

[jira] [Commented] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282927#comment-15282927 ] Wangda Tan commented on YARN-5082: -- CS has similar issue. (Linked) > ContainerId rapidly increased in

[jira] [Commented] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282911#comment-15282911 ] sandflee commented on YARN-5082: we enable continuous scheduling, so containerID increased (corresponding

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282902#comment-15282902 ] Hitesh Shah commented on YARN-5079: --- It might be better to have this discussion on the mailing lists

[jira] [Created] (YARN-5082) ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit

sandflee created YARN-5082: -- Summary: ContainerId rapidly increased in fair scheduler if the num of node app reserved reached the limit Key: YARN-5082 URL: https://issues.apache.org/jira/browse/YARN-5082

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

[ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282883#comment-15282883 ] Jian He commented on YARN-4832: --- bq. What do you think? Yeah, sounds good to me. > NM side resource value

[jira] [Commented] (YARN-4866) FairScheduler: AMs can consume all vcores leading to a livelock when using FAIR policy

[ https://issues.apache.org/jira/browse/YARN-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282855#comment-15282855 ] Yufei Gu commented on YARN-4866: Test failures are unrelated to the patch. > FairScheduler: AMs can

[jira] [Commented] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link

[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282826#comment-15282826 ] Robert Kanter commented on YARN-5041: - [~haibochen], it looks like Jenkins ran, but didn't post a

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

[ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282763#comment-15282763 ] Junping Du commented on YARN-4832: -- Thanks for review and comments, Jian! bq. I'm thinking of a simpler

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282754#comment-15282754 ] Varun Vasudev commented on YARN-4913: - [~xgong] - couple of issues with the latest patch - # Can you

[jira] [Commented] (YARN-4325) Purge app state from NM state-store should cover more LOG_HANDLING cases

[ https://issues.apache.org/jira/browse/YARN-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282726#comment-15282726 ] Jason Lowe commented on YARN-4325: -- Appears Jenkins is having difficulty posting to JIRA. Overall was +1

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888.010.patch Updating patch to fix some findbugs / checkstyle warnings.. >

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282689#comment-15282689 ] Eric Payne commented on YARN-3362: -- Thanks, [~naganarasimha...@apache.org]. Have you been able to look at

[jira] [Commented] (YARN-4325) Purge app state from NM state-store should cover more LOG_HANDLING cases

[ https://issues.apache.org/jira/browse/YARN-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282658#comment-15282658 ] Junping Du commented on YARN-4325: -- The Jenkins doesn't get triggered automatically for some reason...

[jira] [Commented] (YARN-4721) RM to try to auth with HDFS on startup, retry with max diagnostics on failure

[ https://issues.apache.org/jira/browse/YARN-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282657#comment-15282657 ] Junping Du commented on YARN-4721: -- [~ste...@apache.org], any update on the patch? > RM to try to auth

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282654#comment-15282654 ] Junping Du commented on YARN-679: - Sounds like Jenkins not get started as last time. Kick off Jenkins

[jira] [Commented] (YARN-4837) User facing aspects of 'AM blacklisting' feature need fixing

[ https://issues.apache.org/jira/browse/YARN-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282652#comment-15282652 ] Junping Du commented on YARN-4837: -- Sounds good to me. We can mark it to be private first. > User facing

[jira] [Commented] (YARN-5080) Cannot obtain logs using YARN CLI -am for either KILLED or RUNNING AM

[ https://issues.apache.org/jira/browse/YARN-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282651#comment-15282651 ] Junping Du commented on YARN-5080: -- +1. Patch LGTM. Will commit it shortly. > Cannot obtain logs using

[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 ] Harish Jaiprakash updated YARN-5068: Attachment: YARN-5068-branch-2.1.patch Thanks Rohith. Created patch file for branch-2. >

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282649#comment-15282649 ] Junping Du commented on YARN-679: - I am general Ok with proposed APIs. But I was waiting for Jenkins report

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282633#comment-15282633 ] Steve Loughran commented on YARN-679: - have you had a chance yet? > add an entry point that can start