[jira] [Assigned] (YARN-10934) LeafQueue activateApplications NPE

[ https://issues.apache.org/jira/browse/YARN-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10934: Assignee: Benjamin Teke > LeafQueue activateApplications NPE >

[jira] [Resolved] (YARN-10496) [Umbrella] Support Flexible Auto Queue Creation in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-10496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke resolved YARN-10496. -- Resolution: Fixed > [Umbrella] Support Flexible Auto Queue Creation in Capacity Scheduler >

[jira] [Assigned] (YARN-10872) Replace getPropsWithPrefix calls in AutoCreatedQueueTemplate

[ https://issues.apache.org/jira/browse/YARN-10872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10872: Assignee: Benjamin Teke (was: Andras Gyori) > Replace getPropsWithPrefix calls in

[jira] [Commented] (YARN-10872) Replace getPropsWithPrefix calls in AutoCreatedQueueTemplate

[ https://issues.apache.org/jira/browse/YARN-10872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410696#comment-17410696 ] Benjamin Teke commented on YARN-10872: -- As per the offline discussion with [~gandras] I'm taking

[jira] [Assigned] (YARN-10909) AbstractCSQueue: Check for methods added for test code but not annotated with VisibleForTesting

[ https://issues.apache.org/jira/browse/YARN-10909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10909: Assignee: (was: Andrew Wang) > AbstractCSQueue: Check for methods added for test code

[jira] [Assigned] (YARN-10909) AbstractCSQueue: Check for methods added for test code but not annotated with VisibleForTesting

[ https://issues.apache.org/jira/browse/YARN-10909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10909: Assignee: Andrew Wang > AbstractCSQueue: Check for methods added for test code but not

[jira] [Updated] (YARN-10646) TestCapacitySchedulerWeightMode test descriptor comments doesn't reflect the correct scenario

[ https://issues.apache.org/jira/browse/YARN-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10646: - Parent Issue: YARN-10889 (was: YARN-10888) > TestCapacitySchedulerWeightMode test descriptor

[jira] [Commented] (YARN-10576) Update Capacity Scheduler documentation about JSON-based placement mapping

[ https://issues.apache.org/jira/browse/YARN-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404544#comment-17404544 ] Benjamin Teke commented on YARN-10576: -- [~pbacsko] thanks, took it over. Uploaded a PR with the

[jira] [Assigned] (YARN-10576) Update Capacity Scheduler documentation about JSON-based placement mapping

[ https://issues.apache.org/jira/browse/YARN-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10576: Assignee: Benjamin Teke (was: Peter Bacsko) > Update Capacity Scheduler documentation

[jira] [Commented] (YARN-10522) Document for Flexible Auto Queue Creation in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403903#comment-17403903 ] Benjamin Teke commented on YARN-10522: -- [~gandras] thanks for the comments. Updated the patch

[jira] [Updated] (YARN-10522) Document for Flexible Auto Queue Creation in Capacity Scheduler.

[ https://issues.apache.org/jira/browse/YARN-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10522: - Attachment: YARN-10522.001.patch > Document for Flexible Auto Queue Creation in Capacity

[jira] [Commented] (YARN-10838) Implement an optimised version of Configuration getPropsWithPrefix

[ https://issues.apache.org/jira/browse/YARN-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401186#comment-17401186 ] Benjamin Teke commented on YARN-10838: -- [~snemeth], I've uploaded a new patch based on your

[jira] [Updated] (YARN-10838) Implement an optimised version of Configuration getPropsWithPrefix

[ https://issues.apache.org/jira/browse/YARN-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10838: - Attachment: YARN-10838.005.patch > Implement an optimised version of Configuration

[jira] [Commented] (YARN-10576) Update Capacity Scheduler documentation about JSON-based placement mapping

[ https://issues.apache.org/jira/browse/YARN-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401153#comment-17401153 ] Benjamin Teke commented on YARN-10576: -- Thanks [~pbacsko] for working on this. One nit: "Differences

[jira] [Commented] (YARN-10049) FIFOOrderingPolicy Improvements

[ https://issues.apache.org/jira/browse/YARN-10049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17401134#comment-17401134 ] Benjamin Teke commented on YARN-10049: -- [~maniraj...@gmail.com] thanks for the patch. I'm guessing

[jira] [Commented] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397403#comment-17397403 ] Benjamin Teke commented on YARN-10505: -- [~epayne] as [~rreti] mentioned we don't plan to change the

[jira] [Commented] (YARN-10693) Add document for YARN-10623 auto refresh queue conf in CS

[ https://issues.apache.org/jira/browse/YARN-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394793#comment-17394793 ] Benjamin Teke commented on YARN-10693: -- [~zhuqi], thanks for the patch! I would rephrase this

[jira] [Comment Edited] (YARN-10693) Add document for YARN-10623 auto refresh queue conf in CS

[ https://issues.apache.org/jira/browse/YARN-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394793#comment-17394793 ] Benjamin Teke edited comment on YARN-10693 at 8/6/21, 2:16 PM: --- [~zhuqi],

[jira] [Commented] (YARN-10844) Add Leveldb Statestore metrics to NM

[ https://issues.apache.org/jira/browse/YARN-10844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394788#comment-17394788 ] Benjamin Teke commented on YARN-10844: -- [~chaosju], thanks for working on this. The patch looks good

[jira] [Updated] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10759: - Attachment: YARN-10759.008.patch > Encapsulate queue config modes >

[jira] [Updated] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10759: - Attachment: YARN-10759.008.patch > Encapsulate queue config modes >

[jira] [Updated] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10759: - Attachment: (was: YARN-10759.008.patch) > Encapsulate queue config modes >

[jira] [Commented] (YARN-10547) Decouple job parsing logic from SLSRunner

[ https://issues.apache.org/jira/browse/YARN-10547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17392336#comment-17392336 ] Benjamin Teke commented on YARN-10547: -- [~snemeth], Thanks for the patch, it seems to me you've

[jira] [Commented] (YARN-10840) yarn app status fails with ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17390013#comment-17390013 ] Benjamin Teke commented on YARN-10840: -- [~abhinaba.sarkar] can you please explain this issue a bit?

[jira] [Assigned] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10505: Assignee: Benjamin Teke > Extend the maximum-capacity property to support Fair Scheduler

[jira] [Updated] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10759: - Attachment: YARN-10759.007.patch > Encapsulate queue config modes >

[jira] [Commented] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388871#comment-17388871 ] Benjamin Teke commented on YARN-10759: -- [~gandras], [~snemeth] after our offline discussion uploaded

[jira] [Commented] (YARN-6272) TestAMRMClient#testAMRMClientWithContainerResourceChange fails intermittently

[ https://issues.apache.org/jira/browse/YARN-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388822#comment-17388822 ] Benjamin Teke commented on YARN-6272: - Thanks [~gandras] for picking this up and the patch. LGTM

[jira] [Commented] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387439#comment-17387439 ] Benjamin Teke commented on YARN-10833: -- [~zhuqi] thanks for commiting this one! > RM logs endpoint

[jira] [Commented] (YARN-10838) Implement an optimised version of Configuration getPropsWithPrefix

[ https://issues.apache.org/jira/browse/YARN-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386372#comment-17386372 ] Benjamin Teke commented on YARN-10838: -- Thanks [~gandras] for working on this. The latest patch

[jira] [Commented] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386268#comment-17386268 ] Benjamin Teke commented on YARN-10833: -- Thanks for the review [~zhuqi]. Szilard took a look at it

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation-mb/vcore property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Description: When using auto created queues even though the default maximum allocation was

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation-mb/vcore property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Description: When using auto created queues even though the default maximum allocation was

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation-mb/vcore property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Summary: CS considers only the default maximum-allocation-mb/vcore property as a maximum when it

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Description: When using auto created queues even though the default maximum allocation was

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Description: When using auto created queues even though the default maximum allocation was

[jira] [Created] (YARN-10869) CS considers only the default maximum-allocation property as a maximum when it creates dynamic queues

Benjamin Teke created YARN-10869: Summary: CS considers only the default maximum-allocation property as a maximum when it creates dynamic queues Key: YARN-10869 URL:

[jira] [Updated] (YARN-10869) CS considers only the default maximum-allocation property as a maximum when it creates dynamic queues

[ https://issues.apache.org/jira/browse/YARN-10869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10869: - Description: When using auto created queues even though the default maximum allocation was

[jira] [Commented] (YARN-10790) Add separate parent and leaf template property

[ https://issues.apache.org/jira/browse/YARN-10790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17384946#comment-17384946 ] Benjamin Teke commented on YARN-10790: -- Thanks [~gandras] for working on this. The patch looks good

[jira] [Assigned] (YARN-10856) Prevent ATS v2 health check REST API call if the ATS service itself is disabled.

[ https://issues.apache.org/jira/browse/YARN-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-10856: Assignee: Benjamin Teke > Prevent ATS v2 health check REST API call if the ATS service

[jira] [Created] (YARN-10850) TimelineService v2 lists containers for all attempts when filtering for one

Benjamin Teke created YARN-10850: Summary: TimelineService v2 lists containers for all attempts when filtering for one Key: YARN-10850 URL: https://issues.apache.org/jira/browse/YARN-10850 Project:

[jira] [Commented] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371951#comment-17371951 ] Benjamin Teke commented on YARN-10833: -- [~gandras], thanks for the review. Fixed the test issues,

[jira] [Updated] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10833: - Attachment: YARN-10833.002.patch > RM logs endpoint vulnerable to clickjacking >

[jira] [Updated] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10833: - Description: The /logs endpoint is missing the X-FRAME-OPTIONS in the response header, even

[jira] [Updated] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10833: - Attachment: YARN-10833.001.patch > RM logs endpoint vulnerable to clickjacking >

[jira] [Updated] (YARN-10833) RM logs endpoint vulnerable to clickjacking

[ https://issues.apache.org/jira/browse/YARN-10833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10833: - Description: The /logs endpoint is missing the x-frame options in the response header, even

[jira] [Created] (YARN-10833) RM logs endpoint vulnerable to clickjacking

Benjamin Teke created YARN-10833: Summary: RM logs endpoint vulnerable to clickjacking Key: YARN-10833 URL: https://issues.apache.org/jira/browse/YARN-10833 Project: Hadoop YARN Issue Type:

[jira] [Comment Edited] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369503#comment-17369503 ] Benjamin Teke edited comment on YARN-10802 at 6/25/21, 2:38 PM:

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Description: Capacity Scheduler's minimum-user-limit-percent only accepts integers, which means

[jira] [Comment Edited] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369503#comment-17369503 ] Benjamin Teke edited comment on YARN-10802 at 6/25/21, 2:37 PM:

[jira] [Commented] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369503#comment-17369503 ] Benjamin Teke commented on YARN-10802: -- [~epayne], thanks for the clarification. This actually came

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Description: Capacity Scheduler's minimum-user-limit-percent only accepts integers, which means

[jira] [Commented] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362831#comment-17362831 ] Benjamin Teke commented on YARN-10802: -- Hi [~snemeth], Thanks for checking this. 1. Fixed most of

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Attachment: YARN-10802.004.patch > Change Capacity Scheduler minimum-user-limit-percent to

[jira] [Commented] (YARN-10813) Root queue capacity is not set when using node labels

[ https://issues.apache.org/jira/browse/YARN-10813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362825#comment-17362825 ] Benjamin Teke commented on YARN-10813: -- Thanks [~gandras] for the patch, this indeed seems to be a

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Attachment: YARN-10802.003.patch > Change Capacity Scheduler minimum-user-limit-percent to

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Attachment: YARN-10802.002.patch > Change Capacity Scheduler minimum-user-limit-percent to

[jira] [Updated] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

[ https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10802: - Attachment: YARN-10802.001.patch > Change Capacity Scheduler minimum-user-limit-percent to

[jira] [Created] (YARN-10814) YARN shouldn't start with empty hadoop.http.authentication.signature.secret.file

Benjamin Teke created YARN-10814: Summary: YARN shouldn't start with empty hadoop.http.authentication.signature.secret.file Key: YARN-10814 URL: https://issues.apache.org/jira/browse/YARN-10814

[jira] [Commented] (YARN-10807) Parents node labels are incorrectly added to child queues in weight mode

[ https://issues.apache.org/jira/browse/YARN-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358682#comment-17358682 ] Benjamin Teke commented on YARN-10807: -- [~zhuqi] Thanks for the review. I agree with the suggestion,

[jira] [Updated] (YARN-10807) Parents node labels are incorrectly added to child queues in weight mode

[ https://issues.apache.org/jira/browse/YARN-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10807: - Attachment: YARN-10807.002.patch > Parents node labels are incorrectly added to child queues in

[jira] [Updated] (YARN-10807) Parents node labels are incorrectly added to child queues in weight mode

[ https://issues.apache.org/jira/browse/YARN-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10807: - Attachment: YARN-10807.001.patch > Parents node labels are incorrectly added to child queues in

[jira] [Updated] (YARN-10807) Parents node labels are incorrectly added to child queues in weight mode

[ https://issues.apache.org/jira/browse/YARN-10807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10807: - Summary: Parents node labels are incorrectly added to child queues in weight mode (was: Parent

[jira] [Created] (YARN-10807) Parent node labels are incorrectly added to child queues in weight mode

Benjamin Teke created YARN-10807: Summary: Parent node labels are incorrectly added to child queues in weight mode Key: YARN-10807 URL: https://issues.apache.org/jira/browse/YARN-10807 Project:

[jira] [Commented] (YARN-10789) RM HA startup can fail due to race conditions in ZKConfigurationStore

[ https://issues.apache.org/jira/browse/YARN-10789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17356447#comment-17356447 ] Benjamin Teke commented on YARN-10789: -- Thanks for the patch [~tarunparimi]. The quick fix (with the

[jira] [Commented] (YARN-10796) Capacity Scheduler: dynamic queue cannot scale out properly if its capacity is 0%

[ https://issues.apache.org/jira/browse/YARN-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355820#comment-17355820 ] Benjamin Teke commented on YARN-10796: -- [~pbacsko] the latest patch looks good to me, +1

[jira] [Commented] (YARN-10801) Fix Auto Queue template to properly set all configuration properties

[ https://issues.apache.org/jira/browse/YARN-10801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355812#comment-17355812 ] Benjamin Teke commented on YARN-10801: -- [~gandras] thanks for working on this! An idea for the

[jira] [Commented] (YARN-10522) Document for Flexible Auto Queue Creation in Capacity Scheduler.

[ https://issues.apache.org/jira/browse/YARN-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355784#comment-17355784 ] Benjamin Teke commented on YARN-10522: -- [~akumar] do you plan to work on this? If not can I take it

[jira] [Created] (YARN-10802) Change Capacity Scheduler minimum-user-limit-percent to accept decimal values

Benjamin Teke created YARN-10802: Summary: Change Capacity Scheduler minimum-user-limit-percent to accept decimal values Key: YARN-10802 URL: https://issues.apache.org/jira/browse/YARN-10802 Project:

[jira] [Comment Edited] (YARN-10796) Capacity Scheduler: dynamic queue cannot scale out properly if its capacity is 0%

[ https://issues.apache.org/jira/browse/YARN-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355758#comment-17355758 ] Benjamin Teke edited comment on YARN-10796 at 6/2/21, 2:15 PM: --- [~pbacsko]

[jira] [Commented] (YARN-10796) Capacity Scheduler: dynamic queue cannot scale out properly if its capacity is 0%

[ https://issues.apache.org/jira/browse/YARN-10796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355758#comment-17355758 ] Benjamin Teke commented on YARN-10796: -- [~pbacsko] thanks for the patch. One small thing: since the

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343503#comment-17343503 ] Benjamin Teke commented on YARN-7769: - [~wilfreds], [~snemeth] did some testing, haven't found any

[jira] [Updated] (YARN-10753) Document the removal of FS default queue creation

[ https://issues.apache.org/jira/browse/YARN-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10753: - Attachment: YARN-10753.001.patch > Document the removal of FS default queue creation >

[jira] [Updated] (YARN-10753) Document the removal of FS default queue creation

[ https://issues.apache.org/jira/browse/YARN-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10753: - Attachment: (was: YARN-10753.001.patch) > Document the removal of FS default queue creation

[jira] [Updated] (YARN-10753) Document the removal of FS default queue creation

[ https://issues.apache.org/jira/browse/YARN-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10753: - Attachment: YARN-10753.001.patch > Document the removal of FS default queue creation >

[jira] [Commented] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342657#comment-17342657 ] Benjamin Teke commented on YARN-10505: -- [~pbacsko] thanks for the suggestion, edited the

[jira] [Updated] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10505: - Description: The property root.users.maximum-capacity could mean the following things: * Parent

[jira] [Updated] (YARN-10505) Extend the maximum-capacity property to react to weight mode changes

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10505: - Description: The property root.users.maximum-capacity could mean the following things: *

[jira] [Comment Edited] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342636#comment-17342636 ] Benjamin Teke edited comment on YARN-10505 at 5/11/21, 3:12 PM: After an

[jira] [Updated] (YARN-10505) Extend the maximum-capacity property to support Fair Scheduler migration

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10505: - Summary: Extend the maximum-capacity property to support Fair Scheduler migration (was: Extend

[jira] [Commented] (YARN-10505) Extend the maximum-capacity property to react to weight mode changes

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342636#comment-17342636 ] Benjamin Teke commented on YARN-10505: -- After an offline discussion with [~gandras] I reopened this

[jira] [Updated] (YARN-10505) Extend the maximum-capacity property to react to weight mode changes

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-10505: - Description: The property root.users.maximum-capacity could mean the following things: *

[jira] [Reopened] (YARN-10505) Extend the maximum-capacity property to react to weight mode changes

[ https://issues.apache.org/jira/browse/YARN-10505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reopened YARN-10505: -- > Extend the maximum-capacity property to react to weight mode changes >

[jira] [Commented] (YARN-10759) Encapsulate queue config modes

[ https://issues.apache.org/jira/browse/YARN-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341916#comment-17341916 ] Benjamin Teke commented on YARN-10759: -- Thanks for working on this [~gandras]! The change in general

[jira] [Comment Edited] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339139#comment-17339139 ] Benjamin Teke edited comment on YARN-7769 at 5/4/21, 4:50 PM: -- [~wilfreds],

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339139#comment-17339139 ] Benjamin Teke commented on YARN-7769: - [~wilfreds], [~snemeth] what do we expect from YARN-8951?

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17332593#comment-17332593 ] Benjamin Teke commented on YARN-7769: - [~wilfreds] both options are good to me, maybe it's a bit

[jira] [Comment Edited] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17332593#comment-17332593 ] Benjamin Teke edited comment on YARN-7769 at 4/26/21, 4:58 PM: --- [~wilfreds]

[jira] [Created] (YARN-10753) Document the removal of FS default queue creation

Benjamin Teke created YARN-10753: Summary: Document the removal of FS default queue creation Key: YARN-10753 URL: https://issues.apache.org/jira/browse/YARN-10753 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-10123) Error message around yarn app -stop/start can be improved to highlight that an implementation at framework level is needed for the stop/start functionality to work

[ https://issues.apache.org/jira/browse/YARN-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17330947#comment-17330947 ] Benjamin Teke commented on YARN-10123: -- [~sahuja] thanks for working on this. The change looks good

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320963#comment-17320963 ] Benjamin Teke commented on YARN-7769: - And I fixed the checkstyle issues in the latest patch. > FS

[jira] [Updated] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-7769: Attachment: YARN-7769.003.patch > FS QueueManager should not create default queue at init >

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320806#comment-17320806 ] Benjamin Teke commented on YARN-7769: - Yes, I missed those, thanks. Uploaded a new patch, let's see

[jira] [Updated] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-7769: Attachment: YARN-7769.002.patch > FS QueueManager should not create default queue at init >

[jira] [Updated] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke updated YARN-7769: Attachment: YARN-7769.001.patch > FS QueueManager should not create default queue at init >

[jira] [Assigned] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Teke reassigned YARN-7769: --- Assignee: Benjamin Teke (was: Wilfred Spiegelenburg) > FS QueueManager should not create

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319537#comment-17319537 ] Benjamin Teke commented on YARN-7769: - I see no activity on this for a while now, so I'll take this

[jira] [Commented] (YARN-10676) Improve code quality in TestTimelineAuthenticationFilterForV1

[ https://issues.apache.org/jira/browse/YARN-10676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296138#comment-17296138 ] Benjamin Teke commented on YARN-10676: -- Thanks [~snemeth] for the patch. LGTM (non-binding) from my

[jira] [Comment Edited] (YARN-10642) AsyncDispatcher will stuck introduced by YARN-8995.

[ https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17294633#comment-17294633 ] Benjamin Teke edited comment on YARN-10642 at 3/3/21, 4:17 PM: ---

[jira] [Commented] (YARN-10642) AsyncDispatcher will stuck introduced by YARN-8995.

[ https://issues.apache.org/jira/browse/YARN-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17294633#comment-17294633 ] Benjamin Teke commented on YARN-10642: -- [~zhengchenyu], looked at the patch, LGTM (non-binding).

<    1   2   3   4   5   6   >