[jira] [Updated] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dian Fu updated YARN-3964: -- Attachment: YARN-3964.014.patch > Support NodeLabelsProvider at Resource Manager side >

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939668#comment-14939668 ] Dian Fu commented on YARN-3964: --- Hi [~Naganarasimha], Thanks a lot for your review. Updated the patch

[jira] [Created] (YARN-4216) Containers logs not shown for containers assigned on NM after recovery

Bibin A Chundatt created YARN-4216: -- Summary: Containers logs not shown for containers assigned on NM after recovery Key: YARN-4216 URL: https://issues.apache.org/jira/browse/YARN-4216 Project:

[jira] [Updated] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4216: --- Summary: Container logs not shown for newly assigned containers after NM recovery (was:

[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

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

[jira] [Updated] (YARN-4216) Containers logs not shown for containers assigned on NM after recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4216: --- Attachment: NMLog > Containers logs not shown for containers assigned on NM after recovery >

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939791#comment-14939791 ] Jason Lowe commented on YARN-4216: -- The problem is the NM is thinking it is being torn down _not_ for a

[jira] [Updated] (YARN-4216) Containers logs not shown for containers assigned on NM after recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4216: --- Component/s: nodemanager log-aggregation > Containers logs not shown for

[jira] [Updated] (YARN-4216) Containers logs not shown for containers assigned on NM after recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4216: --- Attachment: yarn-site.xml > Containers logs not shown for containers assigned on NM after

[jira] [Updated] (YARN-4216) Containers logs not shown for containers assigned on NM after recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4216: --- Attachment: ScreenshotFolder.png > Containers logs not shown for containers assigned on NM

[jira] [Updated] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

[ https://issues.apache.org/jira/browse/YARN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neelesh Srinivas Salian updated YARN-3996: -- Attachment: YARN-3996.prelim.patch > YARN-789 (Support for zero capabilities in

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939924#comment-14939924 ] Bibin A Chundatt commented on YARN-4216: So {{yarn --daemon stop nodemanager}} should be considered

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939861#comment-14939861 ] Jason Lowe commented on YARN-3619: -- Thanks for updating the patch! In the future, please do not remove

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939931#comment-14939931 ] Jason Lowe commented on YARN-4216: -- Not necessarily. A nodemanager could also be shutting down due to an

[jira] [Commented] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

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

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939960#comment-14939960 ] Varun Saxena commented on YARN-3864: Updated an initial patch. This can act as base for Web UI work to

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

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

[jira] [Updated] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3864: --- Attachment: YARN-3864-YARN-2928.01.patch > Implement support for querying single app and all apps for

[jira] [Updated] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3864: --- Attachment: (was: YARN-3864-YARN-2928.01.patch) > Implement support for querying single app and

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939830#comment-14939830 ] Bibin A Chundatt commented on YARN-4216: [~jlowe] The problem doesnt happen when NM is killed using

[jira] [Commented] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

[ https://issues.apache.org/jira/browse/YARN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939941#comment-14939941 ] Neelesh Srinivas Salian commented on YARN-3996: --- [~adhoot] will add tests on top of this.

[jira] [Updated] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3864: --- Attachment: YARN-3864-YARN-2928.01.patch > Implement support for querying single app and all apps for

[jira] [Commented] (YARN-4216) Container logs not shown for newly assigned containers after NM recovery

[ https://issues.apache.org/jira/browse/YARN-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939839#comment-14939839 ] Jason Lowe commented on YARN-4216: -- Then I think this is largely a problem of the NM thinking it is being

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

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

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: (was: YARN-4209.002.patch) > RMStateStore FENCED state doesn’t work due to updateFencedState

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: YARN-4209.002.patch > RMStateStore FENCED state doesn’t work due to updateFencedState called by

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939990#comment-14939990 ] Chris Nauroth commented on YARN-3514: - Hello [~vvasudev]. As per prior comments from [~leftnoteasy]

[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 ] Brook Zhou updated YARN-3223: - Attachment: YARN-3223-v0.patch I changed the implementation to add a flag to NodeUpdateSchedulerEvent

[jira] [Created] (YARN-4217) Failed AM attempt retries on same failed host

Eric Payne created YARN-4217: Summary: Failed AM attempt retries on same failed host Key: YARN-4217 URL: https://issues.apache.org/jira/browse/YARN-4217 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4217) Failed AM attempt retries on same failed host

[ https://issues.apache.org/jira/browse/YARN-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940016#comment-14940016 ] Eric Payne commented on YARN-4217: -- One way to fix this would be by blacklisting the bad nodes. However,

[jira] [Commented] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

[ https://issues.apache.org/jira/browse/YARN-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940044#comment-14940044 ] Naganarasimha G R commented on YARN-4215: - Release Audit warnings might not be related to the

[jira] [Commented] (YARN-4217) Failed AM attempt retries on same failed host

[ https://issues.apache.org/jira/browse/YARN-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940072#comment-14940072 ] Varun Vasudev commented on YARN-4217: - [~eepayne] - is this a duplicate of YARN-2005? > Failed AM

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

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

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940177#comment-14940177 ] Wangda Tan commented on YARN-4140: -- Hi [~bibinchundatt], Thanks for update, several minor comments: 1)

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940128#comment-14940128 ] zhihai xu commented on YARN-3619: - Thanks for the good suggestions [~jlowe]! Will do it next time to avoid

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940406#comment-14940406 ] Li Lu commented on YARN-3942: - YARN-4219 opened to track the new leveldb cache storage separately. > Timeline

[jira] [Created] (YARN-4218) Metric for resource*time that was preempted

Chang Li created YARN-4218: -- Summary: Metric for resource*time that was preempted Key: YARN-4218 URL: https://issues.apache.org/jira/browse/YARN-4218 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4219) New levelDB cache storage for timeline v1.5

Li Lu created YARN-4219: --- Summary: New levelDB cache storage for timeline v1.5 Key: YARN-4219 URL: https://issues.apache.org/jira/browse/YARN-4219 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940278#comment-14940278 ] Varun Saxena commented on YARN-3864: [~gtCarrera9], bq. As a big picture I assume there is an

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940307#comment-14940307 ] Jason Lowe commented on YARN-3942: -- I think the best way forward is to get the original patch cleaned up

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940385#comment-14940385 ] zhihai xu commented on YARN-4209: - The release audit warnings was pre-existing. No other issue from Jenkins

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940420#comment-14940420 ] Sangjin Lee commented on YARN-3864: --- Thanks for the patch [~varun_saxena]! I'm away from the desk, and

[jira] [Updated] (YARN-4218) Metric for resource*time that was preempted

[ https://issues.apache.org/jira/browse/YARN-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4218: --- Attachment: (was: YHADOOP-631.wip.patch) > Metric for resource*time that was preempted >

[jira] [Updated] (YARN-4218) Metric for resource*time that was preempted

[ https://issues.apache.org/jira/browse/YARN-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4218: --- Attachment: YARN-4218.wip.patch > Metric for resource*time that was preempted >

[jira] [Updated] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3942: - Attachment: YARN-3942.002.patch Update to the original patch that addresses Jonathan's mkdirs comment and

[jira] [Updated] (YARN-4218) Metric for resource*time that was preempted

[ https://issues.apache.org/jira/browse/YARN-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4218: --- Attachment: YHADOOP-631.wip.patch > Metric for resource*time that was preempted >

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940314#comment-14940314 ] Li Lu commented on YARN-3942: - Thanks for the info [~jlowe]! Sure I can open a new JIRA for the leveldb cache

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940344#comment-14940344 ] Li Lu commented on YARN-3864: - bq. I guess we can get flow runs from /flows endpoint and then for each flow

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940381#comment-14940381 ] Sangjin Lee commented on YARN-3864: --- Yes, the apps query (and therefore the application table) is the

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940551#comment-14940551 ] Varun Saxena commented on YARN-3864: Yeah but this is similar to what we do while querying entity.

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

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

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940460#comment-14940460 ] Varun Saxena commented on YARN-3864: bq. I think sortedKeys can/should be private Ok. bq. The URL

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940520#comment-14940520 ] Varun Saxena commented on YARN-3864: [~vrushalic] bq. For the /app endpoint, I think we need only the

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940537#comment-14940537 ] Vrushali C commented on YARN-3864: -- bq. In first one, cluster id will be taken from config and in the next

[jira] [Commented] (YARN-3864) Implement support for querying single app and all apps for a flow run

[ https://issues.apache.org/jira/browse/YARN-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940489#comment-14940489 ] Vrushali C commented on YARN-3864: -- Thanks [~varun_saxena]! - For the /app endpoint, I think we need only

[jira] [Created] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

Li Lu created YARN-4220: --- Summary: [Storage implementation] Support getEntities with only Application id but no flow and flow run ID Key: YARN-4220 URL: https://issues.apache.org/jira/browse/YARN-4220 Project:

[jira] [Updated] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4220: Priority: Minor (was: Major) > [Storage implementation] Support getEntities with only Application id but no > flow

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940556#comment-14940556 ] Li Lu commented on YARN-4220: - Well, seems like flow and flowrun ids can be easily cached on the client side.

[jira] [Updated] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3619: Attachment: YARN-3619.001.patch > ContainerMetrics unregisters during getMetrics and leads to >

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

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

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

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

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: YARN-4209.002.patch > RMStateStore FENCED state doesn’t work due to updateFencedState called by

[jira] [Updated] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3619: Attachment: (was: YARN-3619.001.patch) > ContainerMetrics unregisters during getMetrics and leads to >

[jira] [Commented] (YARN-4215) RMNodeLabels Manager Need to verify and replace node labels for the only modified Node Label Mappings in the request

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

[jira] [Commented] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939400#comment-14939400 ] zhihai xu commented on YARN-3619: - [~jlowe], thanks for the review! Yes, that is a very good suggestion. I

[jira] [Updated] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

[ https://issues.apache.org/jira/browse/YARN-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-4209: Attachment: (was: YARN-4209.002.patch) > RMStateStore FENCED state doesn’t work due to updateFencedState

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

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

[jira] [Commented] (YARN-4210) HBase reader throws NPE if Get returns no rows

[ https://issues.apache.org/jira/browse/YARN-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939596#comment-14939596 ] Varun Saxena commented on YARN-4210: Thanks [~vrushalic] for the review and commit. And Li and Sangjin

[jira] [Commented] (YARN-4209) RMStateStore FENCED state doesn’t work due to updateFencedState called by stateMachine.doTransition

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

[jira] [Commented] (YARN-3514) Active directory usernames like domain\login cause YARN failures

[ https://issues.apache.org/jira/browse/YARN-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939530#comment-14939530 ] Varun Vasudev commented on YARN-3514: - [~leftnoteasy], [~cnauroth] - can the latest patch be committed?