[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.001.patch Added working code with Unit test Metrics for container's actual

[jira] [Resolved] (YARN-3184) Inefficient iteration of map

[ https://issues.apache.org/jira/browse/YARN-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-3184. - Resolution: Duplicate Inefficient iteration of map

[jira] [Created] (YARN-3184) Inefficient iteration of map

Anubhav Dhoot created YARN-3184: --- Summary: Inefficient iteration of map Key: YARN-3184 URL: https://issues.apache.org/jira/browse/YARN-3184 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3184) Inefficient iteration of map

[ https://issues.apache.org/jira/browse/YARN-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3184: Attachment: YARN-3184.001.patch Use entrySet instead of keySet Inefficient iteration of map

[jira] [Commented] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14312262#comment-14312262 ] Anubhav Dhoot commented on YARN-3122: - On a 4 proc machine the parent process 1778 has

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.prelim.patch Preliminary patch to calculate CPU VCores used for

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Attachment: YARN-3122.prelim.patch [ ]# stress -c 3 [1] 1778 [ ]# stress: info: [1778] dispatching

[jira] [Commented] (YARN-3101) In Fair Scheduler, fix canceling of reservations for exceeding max share

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14307689#comment-14307689 ] Anubhav Dhoot commented on YARN-3101: - Thanks [~sandyr] for the review and commit. In

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.004.patch FairScheduler#fitInMaxShare was added to validate reservations but

[jira] [Created] (YARN-3138) TestFairScheduler#testContinuousScheduling fails intermittently on trunk

Anubhav Dhoot created YARN-3138: --- Summary: TestFairScheduler#testContinuousScheduling fails intermittently on trunk Key: YARN-3138 URL: https://issues.apache.org/jira/browse/YARN-3138 Project: Hadoop

[jira] [Resolved] (YARN-3138) TestFairScheduler#testContinuousScheduling fails intermittently on trunk

[ https://issues.apache.org/jira/browse/YARN-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-3138. - Resolution: Duplicate TestFairScheduler#testContinuousScheduling fails intermittently on trunk

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.004.patch After offline discussions with [~sandyr] added an additional check

[jira] [Commented] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304170#comment-14304170 ] Anubhav Dhoot commented on YARN-3119: - Thanks for the comments. Just wanted to give a

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301971#comment-14301971 ] Anubhav Dhoot commented on YARN-3101: - YARN-1778 (TestFSRMStateStore) and YARN-3113

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

[ https://issues.apache.org/jira/browse/YARN-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3121: Attachment: yARN-3121.prelim.patch attaching premlinary patch showing all the metrics.

[jira] [Commented] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301698#comment-14301698 ] Anubhav Dhoot commented on YARN-3119: - Thanks [~leftnoteasy], [~aw] for your comments.

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

[ https://issues.apache.org/jira/browse/YARN-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3121: Attachment: yARN-3121.prelim.patch FairScheduler preemption metrics

[jira] [Commented] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299304#comment-14299304 ] Anubhav Dhoot commented on YARN-3119: - The scheduling should continue like before where

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299348#comment-14299348 ] Anubhav Dhoot commented on YARN-3101: - Hi [~l201514] why do we need to make the

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299396#comment-14299396 ] Anubhav Dhoot commented on YARN-3101: - The test case was modified to add a negative

[jira] [Commented] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299570#comment-14299570 ] Anubhav Dhoot commented on YARN-3122: - Similar to YARN-2984 this would track CPU usage

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Description: It would be nice to capture resource usage per container, for a variety of reasons.

[jira] [Updated] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3122: Fix Version/s: (was: 2.7.0) Metrics for container's actual CPU usage

[jira] [Assigned] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3122: --- Assignee: Anubhav Dhoot (was: Karthik Kambatla) Metrics for container's actual CPU usage

[jira] [Created] (YARN-3122) Metrics for container's actual CPU usage

Anubhav Dhoot created YARN-3122: --- Summary: Metrics for container's actual CPU usage Key: YARN-3122 URL: https://issues.apache.org/jira/browse/YARN-3122 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.003.patch Reverts changes from test case

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

[ https://issues.apache.org/jira/browse/YARN-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3121: --- Assignee: Anubhav Dhoot FairScheduler preemption metrics

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

Anubhav Dhoot created YARN-3121: --- Summary: FairScheduler preemption metrics Key: YARN-3121 URL: https://issues.apache.org/jira/browse/YARN-3121 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299689#comment-14299689 ] Anubhav Dhoot commented on YARN-3101: - The failure does not repro after pulling the

[jira] [Updated] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3119: Component/s: nodemanager Memory limit check need not be enforced unless aggregate usage of all

[jira] [Assigned] (YARN-3119) Memory limit check need not be enforced unless aggregate usage of all containers is near limit

[ https://issues.apache.org/jira/browse/YARN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3119: --- Assignee: Anubhav Dhoot Memory limit check need not be enforced unless aggregate usage of

[jira] [Commented] (YARN-3094) reset timer for liveness monitors after RM recovery

[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295814#comment-14295814 ] Anubhav Dhoot commented on YARN-3094: - Hi [~Jun Gong] Can you please use the

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296059#comment-14296059 ] Anubhav Dhoot commented on YARN-3021: - We are talking about turning off renewal of

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295664#comment-14295664 ] Anubhav Dhoot commented on YARN-3101: - YARN-2811 added the following {noformat} private

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.002.patch Updated test to add negative test case (should not drop reservation

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294060#comment-14294060 ] Anubhav Dhoot commented on YARN-3079: - LGTM Verified that the nodeUpdate is called from

[jira] [Assigned] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2868: --- Assignee: Anubhav Dhoot (was: Ray Chiang) Add metric for initial container launch time to

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294431#comment-14294431 ] Anubhav Dhoot commented on YARN-2868: - Hi [~leftnoteasy] RMAppMetrics will be

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.003.patch Addressed feedback Expose Container resource information from

[jira] [Created] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

Anubhav Dhoot created YARN-3101: --- Summary: FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it Key: YARN-3101 URL: https://issues.apache.org/jira/browse/YARN-3101

[jira] [Assigned] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3101: --- Assignee: Anubhav Dhoot FairScheduler#fitInMaxShare was added to validate reservations but

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.001.patch Fixes the issue Verified the test passes

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293010#comment-14293010 ] Anubhav Dhoot commented on YARN-3101: - [~sandyr] [~l201514] appreciate your review

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290042#comment-14290042 ] Anubhav Dhoot commented on YARN-3079: - Should we add a couple of more combinations to

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290420#comment-14290420 ] Anubhav Dhoot commented on YARN-2868: - Adding it to ClusterMetrics will only give you a

[jira] [Commented] (YARN-2868) Add metric for initial container launch time

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14288431#comment-14288431 ] Anubhav Dhoot commented on YARN-2868: - volatile cannot be used for thread

[jira] [Updated] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3082: Attachment: YARN-3082.002.patch Addressed feedback Non thread safe access to systemCredentials in

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.002.patch Rebased, added unit tests. Also removed an overload of forContainer

[jira] [Created] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

Anubhav Dhoot created YARN-3082: --- Summary: Non thread safe access to systemCredentials in NodeHeartbeatResponse processing Key: YARN-3082 URL: https://issues.apache.org/jira/browse/YARN-3082 Project:

[jira] [Updated] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3082: Attachment: YARN-3082.001.patch Attaches patch that ensures ByteBuffer which ends up getting shared

[jira] [Commented] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14286860#comment-14286860 ] Anubhav Dhoot commented on YARN-3082: - We have seen examples with running on a secure

[jira] [Commented] (YARN-2990) FairScheduler's delay-scheduling always waits for node-local and rack-local delays, even for off-rack-only requests

[ https://issues.apache.org/jira/browse/YARN-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14281606#comment-14281606 ] Anubhav Dhoot commented on YARN-2990: - Can anyNodeLocalRequests work by simply checking

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279109#comment-14279109 ] Anubhav Dhoot commented on YARN-3021: - I don't see any security holes. This token is

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14275797#comment-14275797 ] Anubhav Dhoot commented on YARN-3021: - Looking at the patch itself we seem to suppress

[jira] [Updated] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3027: Attachment: YARN-3027.002.patch Added unchecked to suppress warnings Scheduler should use

[jira] [Commented] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14272341#comment-14272341 ] Anubhav Dhoot commented on YARN-3027: - Test Failure is unrelated Scheduler should use

[jira] [Created] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

Anubhav Dhoot created YARN-3027: --- Summary: Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation Key: YARN-3027 URL: https://issues.apache.org/jira/browse/YARN-3027

[jira] [Updated] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3027: Attachment: YARN-3027.001.patch Use totalresource instead of available resource and unit test

[jira] [Created] (YARN-3022) Expose Container resource information from NodeManager for monitoring

Anubhav Dhoot created YARN-3022: --- Summary: Expose Container resource information from NodeManager for monitoring Key: YARN-3022 URL: https://issues.apache.org/jira/browse/YARN-3022 Project: Hadoop YARN

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.001.patch Initial patch based on YARN-2984 which adds metrics for Containers

[jira] [Commented] (YARN-2984) Metrics for container's actual memory usage

[ https://issues.apache.org/jira/browse/YARN-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14269944#comment-14269944 ] Anubhav Dhoot commented on YARN-2984: - Seems good. I tested it and shows up on the jmx

[jira] [Resolved] (YARN-2574) Add support for FairScheduler to the ReservationSystem

[ https://issues.apache.org/jira/browse/YARN-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-2574. - Resolution: Fixed Fix Version/s: 2.7.0 Add support for FairScheduler to the

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Issue Type: Bug (was: Sub-task) Parent: (was: YARN-2574) Use

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Component/s: (was: fairscheduler) Use ReservationQueueConfiguration in CapacityScheduler

[jira] [Created] (YARN-3008) FairScheduler: Use lock for queuemanager instead of synchronized on FairScheduler

Anubhav Dhoot created YARN-3008: --- Summary: FairScheduler: Use lock for queuemanager instead of synchronized on FairScheduler Key: YARN-3008 URL: https://issues.apache.org/jira/browse/YARN-3008 Project:

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262667#comment-14262667 ] Anubhav Dhoot commented on YARN-2881: - I removed it because both are ultimately called

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.006.patch Addressed all comments. Regarding moving PlanQueue, i moved the

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.002.patch Kicking jenkins again as the failures seem unrelated Implement

[jira] [Assigned] (YARN-2998) Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2998: --- Assignee: Anubhav Dhoot Abstract out scheduler independant PlanFollower components into

[jira] [Created] (YARN-2998) Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower

Anubhav Dhoot created YARN-2998: --- Summary: Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower Key: YARN-2998 URL: https://issues.apache.org/jira/browse/YARN-2998

[jira] [Updated] (YARN-2998) Abstract out scheduler independent PlanFollower components

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2998: Attachment: YARN-2998.001.patch Creates AbstractSchedulerPlanFollower Abstract out scheduler

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261630#comment-14261630 ] Anubhav Dhoot commented on YARN-2881: - Added patch that builds on top of YARN-2998

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.003.patch Implement PlanFollower for FairScheduler

[jira] [Updated] (YARN-2998) Abstract out scheduler independent PlanFollower components

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2998: Attachment: YARN-2998.003.patch Addressed feedback Abstract out scheduler independent PlanFollower

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.004.patch Moved code factored from YARN-2998 Implement PlanFollower for

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.005.patch Updated for the renamed methods in YARN-2998 Implement

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14260491#comment-14260491 ] Anubhav Dhoot commented on YARN-2881: - Hi [~subru] thanks for your review bq. Are you

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.002.patch Addressing [~subru]'s comments and FindBugs Implement PlanFollower

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.001.patch Implements rest of the Fair Scheduler Reservation system. Tested

[jira] [Commented] (YARN-2664) Improve RM webapp to expose info about reservations.

[ https://issues.apache.org/jira/browse/YARN-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14255533#comment-14255533 ] Anubhav Dhoot commented on YARN-2664: - Overall this is a very natural way to visualize

[jira] [Created] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

Anubhav Dhoot created YARN-2982: --- Summary: Use ReservationQueueConfiguration in CapacityScheduler Key: YARN-2982 URL: https://issues.apache.org/jira/browse/YARN-2982 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Parent Issue: YARN-2574 (was: YARN-2572) Use ReservationQueueConfiguration in CapacityScheduler

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254212#comment-14254212 ] Anubhav Dhoot commented on YARN-2738: - Re 1. This is a configuration point which will

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254223#comment-14254223 ] Anubhav Dhoot commented on YARN-2975: - Minor comment: The following comment might be

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252343#comment-14252343 ] Anubhav Dhoot commented on YARN-2975: - Yes I am worried about getting it wrong for

[jira] [Commented] (YARN-2868) Add metric for initial container launch time

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250541#comment-14250541 ] Anubhav Dhoot commented on YARN-2868: - Minor nits: FSQueueMetrics has some unused

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250941#comment-14250941 ] Anubhav Dhoot commented on YARN-2975: - The removeApp from one operation is now 2 steps.

[jira] [Updated] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2738: Attachment: YARN-2738.004.patch Addressed all feedback Allowed configuring the class names at the

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14243871#comment-14243871 ] Anubhav Dhoot commented on YARN-2738: - resolveReservationQueueName and

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14241570#comment-14241570 ] Anubhav Dhoot commented on YARN-2877: - +1 for notion of distributed scheduling. I think

[jira] [Created] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

Anubhav Dhoot created YARN-2931: --- Summary: PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner Key: YARN-2931 URL: https://issues.apache.org/jira/browse/YARN-2931

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Description: When the data directory is cleaned up and NM is started with existing recovery state,

[jira] [Assigned] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2931: --- Assignee: Anubhav Dhoot PublicLocalizer may fail with FileNotFoundException until directory

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.001.patch Let PublicLocalizer also initialize the local directories similar to

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.002.patch Fixed javac warnings PublicLocalizer may fail with

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.002.patch PublicLocalizer may fail with FileNotFoundException until directory

[jira] [Commented] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238725#comment-14238725 ] Anubhav Dhoot commented on YARN-2931: - Findbugs donot seem related to the patch.

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.003.patch Addressed comments and made test more robust to verifying the fix

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.004.patch PublicLocalizer may fail with FileNotFoundException until directory

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.005.patch Fixed the dead store findbugs PublicLocalizer may fail with

<    1   2   3   4   5   6   >