[jira] [Commented] (YARN-9690) Invalid AMRM token when distributed scheduling is enabled.

[ https://issues.apache.org/jira/browse/YARN-9690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890681#comment-16890681 ] Bibin A Chundatt commented on YARN-9690: [~Babbleshack] Looks like the AM is trying to connect RM

[jira] [Commented] (YARN-9691) canceling upgrade does not work if upgrade failed container is existing

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

[jira] [Updated] (YARN-9692) ContainerAllocationExpirer is missspelled

[ https://issues.apache.org/jira/browse/YARN-9692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhou wu updated YARN-9692: - Attachment: YARN-9692.001.patch > ContainerAllocationExpirer is missspelled >

[jira] [Commented] (YARN-9692) ContainerAllocationExpirer is missspelled

[ https://issues.apache.org/jira/browse/YARN-9692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890641#comment-16890641 ] runzhou wu commented on YARN-9692: -- The fully name is 

[jira] [Created] (YARN-9692) ContainerAllocationExpirer is missspelled

runzhou wu created YARN-9692: Summary: ContainerAllocationExpirer is missspelled Key: YARN-9692 URL: https://issues.apache.org/jira/browse/YARN-9692 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-9691) canceling upgrade does not work if upgrade failed container is existing

kyungwan nam created YARN-9691: -- Summary: canceling upgrade does not work if upgrade failed container is existing Key: YARN-9691 URL: https://issues.apache.org/jira/browse/YARN-9691 Project: Hadoop YARN

[jira] [Commented] (YARN-2497) Fair scheduler should support strict node labels

[ https://issues.apache.org/jira/browse/YARN-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890573#comment-16890573 ] Yufei Gu commented on YARN-2497: Hi [~chenzhaohang], AFAIK, FS doesn't support node label in any version.

[jira] [Assigned] (YARN-9537) Add configuration to disable AM preemption

[ https://issues.apache.org/jira/browse/YARN-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu reassigned YARN-9537: -- Assignee: zhoukang > Add configuration to disable AM preemption >

[jira] [Commented] (YARN-9537) Add configuration to disable AM preemption

[ https://issues.apache.org/jira/browse/YARN-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890572#comment-16890572 ] Yufei Gu commented on YARN-9537: Hi [~cane], added you to contributor, and assign this to you. Will you

[jira] [Commented] (YARN-9647) Docker launch fails when local-dirs or log-dirs is unhealthy.

[ https://issues.apache.org/jira/browse/YARN-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890503#comment-16890503 ] Jim Brennan commented on YARN-9647: --- [~ebadger], [~eyang], [~magnum] I think I'm following the

[jira] [Commented] (YARN-9647) Docker launch fails when local-dirs or log-dirs is unhealthy.

[ https://issues.apache.org/jira/browse/YARN-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890443#comment-16890443 ] Eric Badger commented on YARN-9647: --- bq. We can resolve this error by keeping track of the original

[jira] [Commented] (YARN-9647) Docker launch fails when local-dirs or log-dirs is unhealthy.

[ https://issues.apache.org/jira/browse/YARN-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890435#comment-16890435 ] Eric Yang commented on YARN-9647: - [~ebadger], I think the approach taken is ok. We want to filter out

[jira] [Commented] (YARN-9689) Router does not support kerberos proxy when in secure mode

[ https://issues.apache.org/jira/browse/YARN-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890402#comment-16890402 ] Botong Huang commented on YARN-9689: +[~giovanni.fumarola] for help > Router does not support

[jira] [Commented] (YARN-9647) Docker launch fails when local-dirs or log-dirs is unhealthy.

[ https://issues.apache.org/jira/browse/YARN-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890394#comment-16890394 ] Eric Badger commented on YARN-9647: --- [~eyang], [~Jim_Brennan], [~billie.rinaldi], any ideas on how to

[jira] [Commented] (YARN-9647) Docker launch fails when local-dirs or log-dirs is unhealthy.

[ https://issues.apache.org/jira/browse/YARN-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890393#comment-16890393 ] Eric Badger commented on YARN-9647: --- [~magnum], thanks for the explanation. I understand what you mean

[jira] [Commented] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890368#comment-16890368 ] Zoltan Siegl commented on YARN-5106: Uploaded patched for branch-3.1 and branch-3.2  > Provide a

[jira] [Updated] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Siegl updated YARN-5106: --- Attachment: YARN-5106-branch-3.2.001.patch > Provide a builder interface for FairScheduler

[jira] [Updated] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Siegl updated YARN-5106: --- Attachment: YARN-5106-branch-3.1.001.patch > Provide a builder interface for FairScheduler

[jira] [Commented] (YARN-9668) UGI conf doesn't read user overridden configurations on RM and NM startup

[ https://issues.apache.org/jira/browse/YARN-9668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890350#comment-16890350 ] Jonathan Hung commented on YARN-9668: - Thanks Haibo! Committed to branch-3.2, branch-3.1, branch-3.0

[jira] [Updated] (YARN-9668) UGI conf doesn't read user overridden configurations on RM and NM startup

[ https://issues.apache.org/jira/browse/YARN-9668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-9668: Fix Version/s: 3.2.2 3.1.3 3.0.4 > UGI conf doesn't read user

[jira] [Commented] (YARN-9687) Queue headroom check may let unacceptable allocation off when using DominantResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890322#comment-16890322 ] Sunil Govindan commented on YARN-9687: -- Hi [~Tao Yang] Thanks for reporting this issue. Yes, we have

[jira] [Commented] (YARN-9596) QueueMetrics has incorrect metrics when labelled partitions are involved

[ https://issues.apache.org/jira/browse/YARN-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890284#comment-16890284 ] Muhammad Samir Khan commented on YARN-9596: --- CSQueueUtils#updateUsedCapacity is called before

[jira] [Commented] (YARN-9562) Add Java changes for the new RuncContainerRuntime

[ https://issues.apache.org/jira/browse/YARN-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890273#comment-16890273 ] Eric Yang commented on YARN-9562: - [~ebadger] Thank you for the patch. Can we create manifestJson as a

[jira] [Commented] (YARN-9690) Invalid AMRM token when distributed scheduling is enabled.

[ https://issues.apache.org/jira/browse/YARN-9690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890254#comment-16890254 ] Babble Shack commented on YARN-9690: I enabled some additional configuration

[jira] [Updated] (YARN-9690) Invalid AMRM token when distributed scheduling is enabled.

[ https://issues.apache.org/jira/browse/YARN-9690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babble Shack updated YARN-9690: --- Component/s: yarn > Invalid AMRM token when distributed scheduling is enabled. >

[jira] [Created] (YARN-9690) Invalid AMRM token when distributed scheduling is enabled.

Babble Shack created YARN-9690: -- Summary: Invalid AMRM token when distributed scheduling is enabled. Key: YARN-9690 URL: https://issues.apache.org/jira/browse/YARN-9690 Project: Hadoop YARN

[jira] [Comment Edited] (YARN-6514) Fail to launch container when distributed scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890202#comment-16890202 ] Babble Shack edited comment on YARN-6514 at 7/22/19 2:35 PM: - I am

[jira] [Commented] (YARN-6514) Fail to launch container when distributed scheduling is enabled

[ https://issues.apache.org/jira/browse/YARN-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890202#comment-16890202 ] Babble Shack commented on YARN-6514: I am experiencing the same issue [~lvzheng] did you ever get this

[jira] [Commented] (YARN-9687) Queue headroom check may let unacceptable allocation off when using DominantResourceCalculator

[ https://issues.apache.org/jira/browse/YARN-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890170#comment-16890170 ] Weiwei Yang commented on YARN-9687: --- This is related to the core resource calculator, it would be good

[jira] [Created] (YARN-9689) Router does not support kerberos proxy when in secure mode

zhoukang created YARN-9689: -- Summary: Router does not support kerberos proxy when in secure mode Key: YARN-9689 URL: https://issues.apache.org/jira/browse/YARN-9689 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-9689) Router does not support kerberos proxy when in secure mode

[ https://issues.apache.org/jira/browse/YARN-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890069#comment-16890069 ] zhoukang commented on YARN-9689: [~botong] Could help evaluate this?Thanks! > Router does not support