[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387091#comment-14387091 ] Arun Suresh commented on YARN-2962: --- [~varun_saxena], Thanks for the patch. It looks

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390076#comment-14390076 ] Arun Suresh commented on YARN-2962: --- .. alternative to starting the index from the front.

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390074#comment-14390074 ] Arun Suresh commented on YARN-2962: --- Yup.. agreed, star index from the end is a better

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2962: -- Attachment: YARN-2962.3.patch Updating with a few minor fixes. ZKRMStateStore: Limit the number of

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516013#comment-14516013 ] Arun Suresh commented on YARN-3485: --- +1, LGTM Thanks for working on this [~kasha]

[jira] [Updated] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2962: -- Attachment: YARN-2962.2.patch Updating Patch: * Rebased with trunk * As discussed in the comments, the

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526289#comment-14526289 ] Arun Suresh commented on YARN-2962: --- bq. we can simplify it without special hierarchies

[jira] [Updated] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3547: -- Labels: (was: BB2015-05-TBR) FairScheduler: Apps that have no resource demand should not participate

[jira] [Updated] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3547: -- Labels: BB2015-05-TBR (was: ) FairScheduler: Apps that have no resource demand should not participate

[jira] [Updated] (YARN-3395) [Fair Scheduler] Handle the user name correctly when user name is used as default queue name.

[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3395: -- Labels: (was: BB2015-05-TBR) [Fair Scheduler] Handle the user name correctly when user name is used

[jira] [Commented] (YARN-3395) [Fair Scheduler] Handle the user name correctly when user name is used as default queue name.

[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14535070#comment-14535070 ] Arun Suresh commented on YARN-3395: --- Thanks for the patch [~zxu], I have just a minor nit

[jira] [Updated] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2684: -- Labels: BB2015-05-TBR (was: ) FairScheduler should tolerate queue configuration changes across RM

[jira] [Updated] (YARN-2684) FairScheduler should if queue is removed during app recovery

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2684: -- Summary: FairScheduler should if queue is removed during app recovery (was: FairScheduler should

[jira] [Updated] (YARN-2684) FairScheduler should fast-fail if queue is removed during app recovery

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2684: -- Summary: FairScheduler should fast-fail if queue is removed during app recovery (was: FairScheduler

[jira] [Updated] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2684: -- Labels: (was: BB2015-05-TBR) FairScheduler should tolerate queue configuration changes across RM

[jira] [Updated] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-1297: -- Attachment: YARN-1297.3.patch Updating patch.. fixing it up to so it rebases to trunk Miscellaneous

[jira] [Updated] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-1297: -- Attachment: YARN-1297.4.patch Updating patch to fix the test failure * Had missed accounting for app

[jira] [Created] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

Arun Suresh created YARN-3676: - Summary: Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests Key: YARN-3676 URL: https://issues.apache.org/jira/browse/YARN-3676

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549547#comment-14549547 ] Arun Suresh commented on YARN-3655: --- Thanks for the patch [~zxu], I was just wondering

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549949#comment-14549949 ] Arun Suresh commented on YARN-3633: --- Thanks for the patch [~ragarwal], Assuming we allow,

[jira] [Updated] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-1297: -- Labels: (was: BB2015-05-TBR) Miscellaneous Fair Scheduler speedups

[jira] [Updated] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-1297: -- Attachment: YARN-1297.4.patch attaching again to kick off jenkins Miscellaneous Fair Scheduler

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14499939#comment-14499939 ] Arun Suresh commented on YARN-2962: --- [~varun_saxena], wondering if you need any help with

[jira] [Created] (YARN-3470) Make PermissionStatusFormat public

Arun Suresh created YARN-3470: - Summary: Make PermissionStatusFormat public Key: YARN-3470 URL: https://issues.apache.org/jira/browse/YARN-3470 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3676: -- Attachment: YARN-3676.1.patch Attaching initial patch to validate approach.. will include test-case

[jira] [Created] (YARN-3691) Limit number of reservations for an app

Arun Suresh created YARN-3691: - Summary: Limit number of reservations for an app Key: YARN-3691 URL: https://issues.apache.org/jira/browse/YARN-3691 Project: Hadoop YARN Issue Type: Bug

[jira] [Assigned] (YARN-3691) Limit number of reservations for an app

[ https://issues.apache.org/jira/browse/YARN-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-3691: - Assignee: Arun Suresh Limit number of reservations for an app

[jira] [Commented] (YARN-3762) FairScheduler: CME on FSParentQueue#getQueueUserAclInfo

[ https://issues.apache.org/jira/browse/YARN-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571512#comment-14571512 ] Arun Suresh commented on YARN-3762: --- Makes sense +1, LGTM FairScheduler: CME on

[jira] [Updated] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3453: -- Attachment: YARN-3453.2.patch Agreed.. Updating patch with your suggestion.. Fair Scheduler : Parts

[jira] [Assigned] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-3453: - Assignee: Arun Suresh Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator

[jira] [Updated] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3453: -- Attachment: YARN-3453.1.patch [~peng.zhang], [~ashwinshankar77], Thank you reporting this.. and the

[jira] [Commented] (YARN-3762) FairScheduler: CME on FSParentQueue#getQueueUserAclInfo

[ https://issues.apache.org/jira/browse/YARN-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571409#comment-14571409 ] Arun Suresh commented on YARN-3762: --- [~kasha], Thanks for the patch * In the

[jira] [Commented] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615228#comment-14615228 ] Arun Suresh commented on YARN-2154: --- This looks like it is required for a complete

[jira] [Updated] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3676: -- Attachment: YARN-3676.5.patch Disregard 'assignMultiple' directive while scheduling apps with

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554745#comment-14554745 ] Arun Suresh commented on YARN-3655: --- Thanks for the update [~zxu]. I have only one nit :

[jira] [Commented] (YARN-3675) FairScheduler: RM quits when node removal races with continousscheduling on the same node

[ https://issues.apache.org/jira/browse/YARN-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554814#comment-14554814 ] Arun Suresh commented on YARN-3675: --- Thanks for the patch [~adhoot], +1, LGTM

[jira] [Updated] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3676: -- Attachment: YARN-3676.3.patch Updating patch with testcase Disregard 'assignMultiple' directive while

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1466#comment-1466 ] Arun Suresh commented on YARN-3655: --- makes sense... +1 from me.. will commit, unless

[jira] [Updated] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3676: -- Attachment: YARN-3676.4.patch Updating patch * Changed the accounting logic a bit * Improved test case *

[jira] [Updated] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3676: -- Attachment: YARN-3676.2.patch Reattaching patch. Disregard 'assignMultiple' directive while scheduling

[jira] [Commented] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615236#comment-14615236 ] Arun Suresh commented on YARN-3453: --- Apologize for the delay. Thanks for the review

[jira] [Commented] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704320#comment-14704320 ] Arun Suresh commented on YARN-4066: --- [~johang], Thanks for reporting this... I don't

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708318#comment-14708318 ] Arun Suresh commented on YARN-221: -- Looks like trunk does not compile correctly after

[jira] [Commented] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705094#comment-14705094 ] Arun Suresh commented on YARN-4066: --- +1 pending jenkins Large number of queues choke

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609119#comment-14609119 ] Arun Suresh commented on YARN-3633: --- [~ragarwal], Was just wondering.. wrt the scenario

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609278#comment-14609278 ] Arun Suresh commented on YARN-3633: --- I guess the line that was introduced needs to be

[jira] [Commented] (YARN-3633) With Fair Scheduler, cluster can logjam when there are too many queues

[ https://issues.apache.org/jira/browse/YARN-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14609175#comment-14609175 ] Arun Suresh commented on YARN-3633: --- Agreed.. So just so that Im on the same page, the

[jira] [Commented] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647045#comment-14647045 ] Arun Suresh commented on YARN-3920: --- Thanks for the patch [~adhoot], The patch looks

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648488#comment-14648488 ] Arun Suresh commented on YARN-2005: --- Thanks for the patch [~adhoot], Couple of comments:

[jira] [Commented] (YARN-3736) Add RMStateStore apis to store and load accepted reservations for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14648831#comment-14648831 ] Arun Suresh commented on YARN-3736: --- The patch looks mostly good [~adhoot], Some minor

[jira] [Commented] (YARN-3736) Add RMStateStore apis to store and load accepted reservations for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658765#comment-14658765 ] Arun Suresh commented on YARN-3736: --- Looks good. Thanks for the patch [~adhoot] and the

[jira] [Commented] (YARN-3736) Add RMStateStore apis to store and load accepted reservations for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658773#comment-14658773 ] Arun Suresh commented on YARN-3736: --- Committed to trunk and branch-2 Add RMStateStore

[jira] [Updated] (YARN-3961) Expose queue container information (pending, running, reserved) in REST api and yarn top

[ https://issues.apache.org/jira/browse/YARN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3961: -- Attachment: YARN-3961.001.patch Re-uploading last patch to kick jenkins Expose queue container

[jira] [Created] (YARN-4012) Add support more multiple NM types in the SLS

Arun Suresh created YARN-4012: - Summary: Add support more multiple NM types in the SLS Key: YARN-4012 URL: https://issues.apache.org/jira/browse/YARN-4012 Project: Hadoop YARN Issue Type: Bug

[jira] [Assigned] (YARN-4012) Add support more multiple NM types in the SLS

[ https://issues.apache.org/jira/browse/YARN-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-4012: - Assignee: Arun Suresh Add support more multiple NM types in the SLS

[jira] [Updated] (YARN-4012) Add support for multiple NM types in the SLS

[ https://issues.apache.org/jira/browse/YARN-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4012: -- Summary: Add support for multiple NM types in the SLS (was: Add support more multiple NM types in the

[jira] [Updated] (YARN-3961) Expose pending, running and reserved containers of a queue in REST api and yarn top

[ https://issues.apache.org/jira/browse/YARN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3961: -- Affects Version/s: 2.7.2 Expose pending, running and reserved containers of a queue in REST api and

[jira] [Commented] (YARN-3961) Expose pending, running and reserved containers of a queue in REST api and yarn top

[ https://issues.apache.org/jira/browse/YARN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659551#comment-14659551 ] Arun Suresh commented on YARN-3961: --- +1, Thanks for the patch [~adhoot] Committing this

[jira] [Updated] (YARN-3961) Expose pending, running and reserved containers of a queue in REST api and yarn top

[ https://issues.apache.org/jira/browse/YARN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3961: -- Summary: Expose pending, running and reserved containers of a queue in REST api and yarn top (was:

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14654130#comment-14654130 ] Arun Suresh commented on YARN-3176: --- Thanks for the patch [~l201514], The patch itself

[jira] [Commented] (YARN-3736) Add RMStateStore apis to store and load accepted reservations for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14654252#comment-14654252 ] Arun Suresh commented on YARN-3736: --- The FindBugs link seems to be incorrect. The correct

[jira] [Updated] (YARN-3961) Expose pending, running and reserved containers of a queue in REST api and yarn top

[ https://issues.apache.org/jira/browse/YARN-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3961: -- Fix Version/s: 2.8.0 Expose pending, running and reserved containers of a queue in REST api and yarn

[jira] [Commented] (YARN-3926) Extend the YARN resource model for easier resource-type management and profiles

[ https://issues.apache.org/jira/browse/YARN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641865#comment-14641865 ] Arun Suresh commented on YARN-3926: --- Thanks for the proposal [~vvasudev] !! Interesting

[jira] [Updated] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2154: -- Attachment: YARN-2154.1.patch Attaching a proof-of-concept patch. The patch introduces an extra stage

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629253#comment-14629253 ] Arun Suresh commented on YARN-3535: --- The patch looks good !! Thanks for working on this

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629249#comment-14629249 ] Arun Suresh commented on YARN-3535: --- I meant for the FairScheduler... but looks like your

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629394#comment-14629394 ] Arun Suresh commented on YARN-3535: --- bq. I think recoverResourceRequest will not be

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627370#comment-14627370 ] Arun Suresh commented on YARN-3535: --- Apologies for the late suggestion. [~djp], Correct

[jira] [Commented] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

[ https://issues.apache.org/jira/browse/YARN-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627669#comment-14627669 ] Arun Suresh commented on YARN-3656: --- [~imenache], Yup.. makes sense I guess a possible

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627581#comment-14627581 ] Arun Suresh commented on YARN-3535: --- bq. .. then on NM restart, running containers

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627602#comment-14627602 ] Arun Suresh commented on YARN-3535: --- makes sense... thanks for clarifying..

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628688#comment-14628688 ] Arun Suresh commented on YARN-3535: --- bq. This jira fix 2. Kill Container event in CS. So

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628722#comment-14628722 ] Arun Suresh commented on YARN-3535: --- Also... Is it possible to simulate the 2 cases in

[jira] [Updated] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Component/s: resourcemanager fairscheduler capacityscheduler

[jira] [Updated] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Fix Version/s: 2.8.0 ResourceRequest should be restored back to scheduler when RMContainer is killed

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631205#comment-14631205 ] Arun Suresh commented on YARN-3535: --- +1, Committing this shortly. Thanks to everyone

[jira] [Updated] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Summary: Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to

[jira] [Updated] (YARN-3453) Fair Scheduler: Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3453: -- Fix Version/s: 2.8.0 Fair Scheduler: Parts of preemption logic uses DefaultResourceCalculator even in

[jira] [Updated] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Fix Version/s: (was: 2.8.0) 2.7.2 Scheduler must re-request container resources

[jira] [Updated] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3535: -- Target Version/s: 2.7.2 (was: 2.8.0) Scheduler must re-request container resources when RMContainer

[jira] [Commented] (YARN-3535) Scheduler must re-request container resources when RMContainer transitions from ALLOCATED to KILLED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632518#comment-14632518 ] Arun Suresh commented on YARN-3535: --- [~jlowe], yup.. ill check it into the 2.7 branch as

[jira] [Commented] (YARN-3453) Fair Scheduler: Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625019#comment-14625019 ] Arun Suresh commented on YARN-3453: --- Thanks for the reviews [~kasha], [~ashwinshankar77]

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625238#comment-14625238 ] Arun Suresh commented on YARN-3535: --- Thanks for working on this [~peng.zhang]. We seem to

[jira] [Commented] (YARN-2154) FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710324#comment-14710324 ] Arun Suresh commented on YARN-2154: --- Thanks for going thru the patch [~adhoot], [~kasha]

[jira] [Commented] (YARN-3738) Add support for recovery of reserved apps (running under dynamic queues) to Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973046#comment-14973046 ] Arun Suresh commented on YARN-3738: --- I agree that not much can be done about the checkstyle warning and

[jira] [Updated] (YARN-3738) Add support for recovery of reserved apps running under dynamic queues

[ https://issues.apache.org/jira/browse/YARN-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-3738: -- Summary: Add support for recovery of reserved apps running under dynamic queues (was: Add support for

[jira] [Resolved] (YARN-3737) Add support for recovery of reserved apps (running under dynamic queues) to Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-3737. --- Resolution: Done Fix Version/s: 2.8.0 > Add support for recovery of reserved apps (running

[jira] [Commented] (YARN-3738) Add support for recovery of reserved apps running under dynamic queues

[ https://issues.apache.org/jira/browse/YARN-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973052#comment-14973052 ] Arun Suresh commented on YARN-3738: --- Committed this to trunk and branch-2, Thanks for the patch [~subru]

[jira] [Updated] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4310: -- Fix Version/s: 2.8.0 > FairScheduler: Log skipping reservation messages at DEBUG level >

[jira] [Created] (YARN-4310) Reduce log level for certain messages to prevent overrunning log file

Arun Suresh created YARN-4310: - Summary: Reduce log level for certain messages to prevent overrunning log file Key: YARN-4310 URL: https://issues.apache.org/jira/browse/YARN-4310 Project: Hadoop YARN

[jira] [Updated] (YARN-4310) Reduce log level for certain messages to prevent overrunning log file

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4310: -- Attachment: YARN-4310.1.patch Attaching trivial patch > Reduce log level for certain messages to

[jira] [Updated] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4310: -- Attachment: YARN-4310.2.patch [~kasha] thanks for the review... updating patch > FairScheduler: Log

[jira] [Commented] (YARN-4184) Remove update reservation state api from state store as its not used by ReservationSystem

[ https://issues.apache.org/jira/browse/YARN-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002881#comment-15002881 ] Arun Suresh commented on YARN-4184: --- Thanks for the patch [~seanpo03]. it looks fine.. +1 Will commit by

[jira] [Assigned] (YARN-2885) LocalRM: distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-2885: - Assignee: Arun Suresh > LocalRM: distributed scheduling decisions for queueable containers >

[jira] [Commented] (YARN-2882) Introducing container types

[ https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14990881#comment-14990881 ] Arun Suresh commented on YARN-2882: --- Thanks for the patch [~kkaranasos]. The patch looks mostly good. Few

[jira] [Updated] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4270: -- Attachment: YARN-4270.5.patch Thanks for the review [~kasha] !! Updating patch with your suggestions.

[jira] [Commented] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964162#comment-14964162 ] Arun Suresh commented on YARN-3985: --- +1, pending jenkins > Make ReservationSystem persist state using

[jira] [Updated] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4270: -- Issue Type: Bug (was: Improvement) > Limit application resource reservation on nodes for non-node/rack

[jira] [Updated] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4270: -- Issue Type: Improvement (was: Bug) > Limit application resource reservation on nodes for non-node/rack

[jira] [Updated] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4270: -- Fix Version/s: 2.8.0 > Limit application resource reservation on nodes for non-node/rack specific >

  1   2   3   4   5   6   7   8   9   10   >