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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.002.patch Addressed the test failure. Unmanaged AM also executes the

[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-tabpanel&focusedCommentId=14603767#comment-14603767 ] Anubhav Dhoot commented on YARN-2005: - The checkstyle error is unavoid

[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-tabpanel&focusedCommentId=14606549#comment-14606549 ] Anubhav Dhoot commented on YARN-2005: - The getNumActiveNMs gets number of un

[jira] [Commented] (YARN-3800) Simplify inmemory state for ReservationAllocation

[ https://issues.apache.org/jira/browse/YARN-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609174#comment-14609174 ] Anubhav Dhoot commented on YARN-3800: - [~kasha] [~jianhe] appreciate your revie

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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.003.patch Added a call to update nodeHostCount before getting blacklist

[jira] [Commented] (YARN-433) When RM is catching up with node updates then it should not expire acquired containers

[ https://issues.apache.org/jira/browse/YARN-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612651#comment-14612651 ] Anubhav Dhoot commented on YARN-433: LGTM > When RM is catching up with node

[jira] [Created] (YARN-3890) FairScheduler should show the scheduler health metrics similar to ones added in CapacityScheduler

Anubhav Dhoot created YARN-3890: --- Summary: FairScheduler should show the scheduler health metrics similar to ones added in CapacityScheduler Key: YARN-3890 URL: https://issues.apache.org/jira/browse/YARN-3890

[jira] [Commented] (YARN-3121) FairScheduler preemption metrics

[ https://issues.apache.org/jira/browse/YARN-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615882#comment-14615882 ] Anubhav Dhoot commented on YARN-3121: - Took a look at YARN-3293. All the metrics t

[jira] [Created] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

Anubhav Dhoot created YARN-3900: --- Summary: Protobuf layout of yarn_security_token causes errors in other protos that include it Key: YARN-3900 URL: https://issues.apache.org/jira/browse/YARN-3900

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619307#comment-14619307 ] Anubhav Dhoot commented on YARN-3900: - Simply printing EpochProto.toString causes

[jira] [Updated] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3900: Attachment: YARN-3900.001.patch > Protobuf layout of yarn_security_token causes errors in ot

[jira] [Updated] (YARN-3800) Simplify inmemory state for ReservationAllocation

[ https://issues.apache.org/jira/browse/YARN-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3800: Attachment: YARN-3800.005.patch Addressed feedback. I feel the types are already on the left side

[jira] [Commented] (YARN-3800) Simplify inmemory state for ReservationAllocation

[ https://issues.apache.org/jira/browse/YARN-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619767#comment-14619767 ] Anubhav Dhoot commented on YARN-3800: - Test failure seems unrelated and filed as f

[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-tabpanel&focusedCommentId=14620965#comment-14620965 ] Anubhav Dhoot commented on YARN-2005: - [~jlowe] appreciate your review of the upd

[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-tabpanel&focusedCommentId=14621302#comment-14621302 ] Anubhav Dhoot commented on YARN-2005: - Thanks for your comments Sunil. 1. Yes we

[jira] [Commented] (YARN-3800) Reduce storage footprint for ReservationAllocation

[ https://issues.apache.org/jira/browse/YARN-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621509#comment-14621509 ] Anubhav Dhoot commented on YARN-3800: - Thanks [~curino] and [~subru]! >

[jira] [Updated] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3900: Attachment: YARN-3900.001.patch Retriggering jenkins as failures did not repro locally for me

[jira] [Commented] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623091#comment-14623091 ] Anubhav Dhoot commented on YARN-3910: - Hi Varun, Its possible that

[jira] [Commented] (YARN-3910) TestRMAppTransitions#testAppAcceptedAttemptKilled fails on trunk

[ https://issues.apache.org/jira/browse/YARN-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623617#comment-14623617 ] Anubhav Dhoot commented on YARN-3910: - LGTM. Tried out the changes and even if I f

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

Anubhav Dhoot created YARN-3920: --- Summary: FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers Key: YARN-3920 URL: https://issues.apache.org/jira/browse

[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-tabpanel&focusedCommentId=14625689#comment-14625689 ] Anubhav Dhoot commented on YARN-2005: - The actual blacklist is already availabl

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626789#comment-14626789 ] Anubhav Dhoot commented on YARN-3900: - All failures were due to flaky tests with j

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628530#comment-14628530 ] Anubhav Dhoot commented on YARN-3878: - LGTM. Unrelated to this patch there i

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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.004.patch Addressed feedback of adding configuration for threshold Also made

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630209#comment-14630209 ] Anubhav Dhoot commented on YARN-3900: - This is needed for YARN-3736. Without this

[jira] [Updated] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3900: Description: Because of the subdirectory server used in {{hadoop-yarn-project/hadoop-yarn/hadoop

[jira] [Updated] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3900: Attachment: YARN-3900.002.patch Updated patch for recent changes in ContainerTokenIdentifierProto

[jira] [Updated] (YARN-3736) Persist the Plan information, ie. accepted reservations to the RMStateStore for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.001.patch Patch that adds implementation of ReservationSystem state to all the

[jira] [Updated] (YARN-3736) Persist the Plan information, ie. accepted reservations to the RMStateStore for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.001.patch > Persist the Plan information, ie. accepted reservations to

[jira] [Updated] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3878: Attachment: YARN-3878.09_reprorace.pat_h Attaching a patch just to demonstrate the race. Since its

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: yARN-3920.001.patch Patch implements a threshold based on a ratio to the maximum sized

[jira] [Commented] (YARN-3878) AsyncDispatcher can hang while stopping if it is configured for draining events on stop

[ https://issues.apache.org/jira/browse/YARN-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635892#comment-14635892 ] Anubhav Dhoot commented on YARN-3878: - Agree this is ok to ignore > AsyncDis

[jira] [Created] (YARN-3957) FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500

Anubhav Dhoot created YARN-3957: --- Summary: FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500 Key: YARN-3957 URL: https://issues.apache.org/jira/browse/YARN-3957 Project

[jira] [Updated] (YARN-3957) FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500

[ https://issues.apache.org/jira/browse/YARN-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3957: Description: There is a NPE causing the webpage of http://localhost:23188/cluster/scheduler to

[jira] [Updated] (YARN-3957) FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500

[ https://issues.apache.org/jira/browse/YARN-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3957: Attachment: YARN-3957.001.patch > FairScheduler NPE In FairSchedulerQueueInfo causing scheduler p

[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-tabpanel&focusedCommentId=14637501#comment-14637501 ] Anubhav Dhoot commented on YARN-2005: - Hi Jian for apps with default max att

[jira] [Updated] (YARN-3957) FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500

[ https://issues.apache.org/jira/browse/YARN-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3957: Attachment: YARN-3957.002.patch Fix test failure > FairScheduler NPE In FairSchedulerQueueI

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

Anubhav Dhoot created YARN-3961: --- Summary: Expose queue container information (pending, running, reserved) in UI and yarn top Key: YARN-3961 URL: https://issues.apache.org/jira/browse/YARN-3961 Project

[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 ] Anubhav Dhoot updated YARN-3961: Summary: Expose queue container information (pending, running, reserved) in REST api and yarn top

[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 ] Anubhav Dhoot updated YARN-3961: Description: It would be nice to expose container (allocated, pending, reserved) information in the

[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 ] Anubhav Dhoot updated YARN-3961: Attachment: YARN-3961.001.patch Attached patch to add container information to REST API for Capacity

[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 ] Anubhav Dhoot updated YARN-3961: Component/s: capacityscheduler > Expose queue container information (pending, running, reserved)

[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 ] Anubhav Dhoot updated YARN-3961: Attachment: Screen Shot 2015-07-22 at 6.17.38 PM.png Screen Shot 2015-07-22 at

[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 ] Anubhav Dhoot updated YARN-3961: Attachment: Screen Shot 2015-07-22 at 6.28.05 PM.png FairScheduler rest api page > Expose qu

[jira] [Commented] (YARN-3900) Protobuf layout of yarn_security_token causes errors in other protos that include it

[ https://issues.apache.org/jira/browse/YARN-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639591#comment-14639591 ] Anubhav Dhoot commented on YARN-3900: - Thanks [~jianhe] for the review and [~rka

[jira] [Commented] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641343#comment-14641343 ] Anubhav Dhoot commented on YARN-3974: - Thanks Subru for improving these test cases

[jira] [Updated] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3974: Attachment: YARN-3974-v2.patch Patch that removes ParametrizedReservationSystemTestBase and used

[jira] [Commented] (YARN-3957) FairScheduler NPE In FairSchedulerQueueInfo causing scheduler page to return 500

[ https://issues.apache.org/jira/browse/YARN-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643110#comment-14643110 ] Anubhav Dhoot commented on YARN-3957: - Thanks [~kasha] for review and co

[jira] [Commented] (YARN-3736) Persist the Plan information, ie. accepted reservations to the RMStateStore for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643314#comment-14643314 ] Anubhav Dhoot commented on YARN-3736: - Thanks [~subru] for the review. Rebased

[jira] [Updated] (YARN-3736) Persist the Plan information, ie. accepted reservations to the RMStateStore for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.002.patch Removed ReservationId from ReservationAllocationStateProto updated

[jira] [Commented] (YARN-3736) Persist the Plan information, ie. accepted reservations to the RMStateStore for failover

[ https://issues.apache.org/jira/browse/YARN-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643328#comment-14643328 ] Anubhav Dhoot commented on YARN-3736: - bq. It may be better to store Reservati

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

Anubhav Dhoot created YARN-3985: --- Summary: Make ReservationSystem persist state using RMStateStore reservation APIs Key: YARN-3985 URL: https://issues.apache.org/jira/browse/YARN-3985 Project: Hadoop

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Summary: Add RMStateStore apis to store and load accepted reservations for failover (was: Persist

[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-tabpanel&focusedCommentId=14643635#comment-14643635 ] Anubhav Dhoot commented on YARN-3736: - Created YARN-3985 for the storing/upda

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.003.patch Fixed checkstyle issues > Add RMStateStore apis to store and l

[jira] [Commented] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645310#comment-14645310 ] Anubhav Dhoot commented on YARN-3974: - Hi Subru the patch looks mostly good. M

[jira] [Commented] (YARN-3990) AsyncDispatcher may overloaded with RMAppNodeUpdateEvent when Node is connected/disconnected

[ https://issues.apache.org/jira/browse/YARN-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646566#comment-14646566 ] Anubhav Dhoot commented on YARN-3990: - Change looks good. It would be good to ha

[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-tabpanel&focusedCommentId=14646612#comment-14646612 ] Anubhav Dhoot commented on YARN-2005: - I think blacklisting can have lots of poli

[jira] [Commented] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646756#comment-14646756 ] Anubhav Dhoot commented on YARN-3994: - This jira should incorporate support

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

Anubhav Dhoot created YARN-3996: --- Summary: YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305 Key: YARN-3996 URL: https://issues.apache.org/jira/browse/YARN-3996

[jira] [Commented] (YARN-3974) Refactor the reservation system test cases to use parameterized base test

[ https://issues.apache.org/jira/browse/YARN-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647070#comment-14647070 ] Anubhav Dhoot commented on YARN-3974: - LGTM > Refactor the reservation syst

[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-tabpanel&focusedCommentId=14649674#comment-14649674 ] Anubhav Dhoot commented on YARN-2005: - Thanks [~asuresh] for the review 1.

[jira] [Assigned] (YARN-3994) RM should respect AM resource/placement constraints

[ https://issues.apache.org/jira/browse/YARN-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3994: --- Assignee: Anubhav Dhoot > RM should respect AM resource/placement constrai

[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-tabpanel&focusedCommentId=14652496#comment-14652496 ] Anubhav Dhoot commented on YARN-3736: - Thanks [~asuresh] for the review. Regardin

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.004.patch Change version number to next minor version for each state store

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3736: Attachment: YARN-3736.005.patch Addressed findbugs warnings > Add RMStateStore apis to store

[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-tabpanel&focusedCommentId=14654511#comment-14654511 ] Anubhav Dhoot commented on YARN-3920: - I am trying to have a config that works ou

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: yARN-3920.002.patch Updated patch to use the right resourceCalculator and updated unit

[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-tabpanel&focusedCommentId=14658619#comment-14658619 ] Anubhav Dhoot commented on YARN-3736: - Findbugs result is clean h

[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-tabpanel&focusedCommentId=14659048#comment-14659048 ] Anubhav Dhoot commented on YARN-3920: - Yeah that should be possible to do when t

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: yARN-3920.003.patch Attaching patch that updates reservation threshold in sync with

[jira] [Created] (YARN-4021) RuntimeException/YarnRuntimeException sent over to the client can cause client to assume a local fatal failure

Anubhav Dhoot created YARN-4021: --- Summary: RuntimeException/YarnRuntimeException sent over to the client can cause client to assume a local fatal failure Key: YARN-4021 URL: https://issues.apache.org/jira/browse

[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 ] Anubhav Dhoot updated YARN-3961: Attachment: YARN-3961.002.patch Fixed the test case failure > Expose queue container informat

[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-tabpanel&focusedCommentId=14660531#comment-14660531 ] Anubhav Dhoot commented on YARN-3961: - Thanks [~asuresh] for review and co

[jira] [Created] (YARN-4030) Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup

Anubhav Dhoot created YARN-4030: --- Summary: Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup Key: YARN-4030 URL: https://issues.apache.org/jira/browse/YARN-4030

[jira] [Commented] (YARN-4030) Make Nodemanager cgroup usage for container easier to use when its running inside a cgroup

[ https://issues.apache.org/jira/browse/YARN-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662192#comment-14662192 ] Anubhav Dhoot commented on YARN-4030: - We can add an option that makes NM read t

[jira] [Created] (YARN-4032) Corrupted state from a previous version can still cause RM to fail with NPE due to same reasons as YARN-2834

Anubhav Dhoot created YARN-4032: --- Summary: Corrupted state from a previous version can still cause RM to fail with NPE due to same reasons as YARN-2834 Key: YARN-4032 URL: https://issues.apache.org/jira/browse/YARN

[jira] [Updated] (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 ] Anubhav Dhoot updated YARN-3737: Assignee: Subru Krishnan (was: Anubhav Dhoot) > Add support for recovery of reserved apps (runn

[jira] [Created] (YARN-4046) NM container recovery is broken on some linux distro because of syntax of signal

Anubhav Dhoot created YARN-4046: --- Summary: NM container recovery is broken on some linux distro because of syntax of signal Key: YARN-4046 URL: https://issues.apache.org/jira/browse/YARN-4046 Project

[jira] [Updated] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4046: Summary: Applications fail on NM restart on some linux distro because NM container recovery declares

[jira] [Commented] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682284#comment-14682284 ] Anubhav Dhoot commented on YARN-4046: - The error in NodeManager shows {noformat}

[jira] [Commented] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682293#comment-14682293 ] Anubhav Dhoot commented on YARN-4046: - As per GNU linux [documentation|

[jira] [Updated] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4046: Attachment: YARN-4096.001.patch Attaching patch that prefixes "--" when using negative pi

[jira] [Updated] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4046: Description: On a debian machine we have seen node manager recovery of containers fail because the

[jira] [Commented] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14687395#comment-14687395 ] Anubhav Dhoot commented on YARN-4046: - [~cnauroth] appreciate your re

[jira] [Updated] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4046: Attachment: YARN-4046.002.patch Fixed a new checkstyle that was added, the other two are preexisting

[jira] [Updated] (YARN-4046) Applications fail on NM restart on some linux distro because NM container recovery declares AM container as LOST

[ https://issues.apache.org/jira/browse/YARN-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4046: Attachment: YARN-4046.002.patch Fixed whitespace > Applications fail on NM restart on some li

[jira] [Updated] (YARN-4051) ContainerKillEvent is lost when container is In New State and is recovering

[ https://issues.apache.org/jira/browse/YARN-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4051: Component/s: nodemanager > ContainerKillEvent is lost when container is In New State and

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4033: Component/s: fairscheduler > In FairScheduler, parent queues should also display queue sta

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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.005.patch Added a patch that maintains a separate system blacklist for

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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.006.patch Fixed YarnConfiguration unit test. Other failure is not happening

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

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.006.patch reattach patch to trigger jenkins > Blacklisting support

[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-tabpanel&focusedCommentId=14703640#comment-14703640 ] Anubhav Dhoot commented on YARN-2005: - [~jianhe] thanks for your comments bq. R

[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-tabpanel&focusedCommentId=14704209#comment-14704209 ] Anubhav Dhoot commented on YARN-2154: - Apart from this, the patch changes the orde

[jira] [Updated] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4024: Component/s: resourcemanager > YARN RM should avoid unnecessary resolving IP when NMs do

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707290#comment-14707290 ] Anubhav Dhoot commented on YARN-4024: - Hi [~zhiguohong] the fix looks good. We

[jira] [Created] (YARN-4076) FairScheduler does not allow AM to choose which containers to preempt

Anubhav Dhoot created YARN-4076: --- Summary: FairScheduler does not allow AM to choose which containers to preempt Key: YARN-4076 URL: https://issues.apache.org/jira/browse/YARN-4076 Project: Hadoop YARN

[jira] [Created] (YARN-4077) FairScheduler Reservation should wait for most relaxed scheduling delay permitted before issuing reservation

Anubhav Dhoot created YARN-4077: --- Summary: FairScheduler Reservation should wait for most relaxed scheduling delay permitted before issuing reservation Key: YARN-4077 URL: https://issues.apache.org/jira/browse/YARN

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch Attaching a patch based on the multiple of increment approach

[jira] [Updated] (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:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch Updated configuration in FairSchedulerConfiguration > FairSchedu

<    1   2   3   4   5   6   7   >