[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: broken-hier-queues.diff FairSchduler AllocationConfiguration doesn't treat

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: YARN-2134.diff FairSchduler AllocationConfiguration doesn't treat hierarchical

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: AllocationConfiguration doesn't fully qualify queue names with respect to

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Fix Version/s: 2.5.0 FairSchduler AllocationConfiguration doesn't treat hierarchical queues

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: AllocationConfiguration doesn't fully qualify queue names with respect to

[jira] [Commented] (YARN-1864) Fair Scheduler Dynamic Hierarchical User Queues

[ https://issues.apache.org/jira/browse/YARN-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021819#comment-14021819 ] Andrey Stepachev commented on YARN-1864: created queues doesn't respect parent

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021828#comment-14021828 ] Hadoop QA commented on YARN-2134: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: YARN-2134.diff FairSchduler AllocationConfiguration doesn't treat hierarchical

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: (was: YARN-2134.diff) FairSchduler AllocationConfiguration doesn't treat

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021869#comment-14021869 ] Hadoop QA commented on YARN-2134: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021881#comment-14021881 ] Sunil G commented on YARN-1408: --- Thank you Wangda for the comment. I was thinking of using

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: (was: YARN-2134.diff) FairSchduler AllocationConfiguration doesn't treat

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: YARN-2134.diff FairSchduler AllocationConfiguration doesn't treat hierarchical

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14023411#comment-14023411 ] Hadoop QA commented on YARN-2134: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: (was: broken-hier-queues.diff) FairSchduler AllocationConfiguration doesn't

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: Automatically created queues doesn't allow to set default parameters. If queue

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: Automatically created queues (f.e. by queue placement rules) doesn't allow to

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: Automatically created queues (f.e. by queue placement rules) doesn't allow to

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Description: Automatically created queues (f.e. by queue placement rules) doesn't allow to

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: YARN-2134-v2.diff FairSchduler AllocationConfiguration doesn't treat

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: YARN-2134-v2.diff FairSchduler AllocationConfiguration doesn't treat

[jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: --- Attachment: (was: YARN-2134-v2.diff) FairSchduler AllocationConfiguration doesn't treat

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025199#comment-14025199 ] Hadoop QA commented on YARN-2134: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025208#comment-14025208 ] Hudson commented on YARN-1368: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1769 (See

[jira] [Commented] (YARN-2075) TestRMAdminCLI consistently fail on trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025268#comment-14025268 ] Rushabh S Shah commented on YARN-2075: -- [~zjshen]: HAAdmin#getTargetIds is a generic

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025274#comment-14025274 ] Wangda Tan commented on YARN-1408: -- [~sunilg], This approach looks good to me.

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025271#comment-14025271 ] Hudson commented on YARN-1368: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1796 (See

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025314#comment-14025314 ] Jason Lowe commented on YARN-1424: -- -1 was chosen to explicitly mark the field as having

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025332#comment-14025332 ] Ray Chiang commented on YARN-1424: -- [~kasha] should I go back to using -1 as the invalid

[jira] [Updated] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1879: - Attachment: YARN-1879.8.patch Rebased on trunk. Mark Idempotent/AtMostOnce annotations to

[jira] [Updated] (YARN-1339) Recover DeletionService state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1339: - Attachment: YARN-1339v5.patch Refreshed patch to trunk. Recover DeletionService state upon nodemanager

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025396#comment-14025396 ] Tsuyoshi OZAWA commented on YARN-2130: -- Thank you for the suggestions, Karthik. Yes, I

[jira] [Commented] (YARN-1709) Admission Control: Reservation subsystem

[ https://issues.apache.org/jira/browse/YARN-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025401#comment-14025401 ] Chris Douglas commented on YARN-1709: - First pass: {{RLE::addInterval/removeInterval}}

[jira] [Resolved] (YARN-1371) FIFO scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1371. --- Resolution: Duplicate Fix Version/s: 2.5.0 Assignee: Jian He

[jira] [Resolved] (YARN-1369) Capacity scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1369. --- Resolution: Duplicate Fix Version/s: 2.5.0 Assignee: Jian He

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025414#comment-14025414 ] Karthik Kambatla commented on YARN-1424: Thanks Jason. I think it makes sense to

[jira] [Updated] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2030: -- Attachment: YARN-2030.v6.patch Use StateMachine to simplify handleStoreEvent() in RMStateStore

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025421#comment-14025421 ] Jian He commented on YARN-2030: --- Patch looks good to me, did a minor rename from operand -

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025451#comment-14025451 ] Vinod Kumar Vavilapalli commented on YARN-2030: --- Quickly looked at it. Fine

[jira] [Created] (YARN-2135) Distributed shell should support passing generic parameters from cli

Karam Singh created YARN-2135: - Summary: Distributed shell should support passing generic parameters from cli Key: YARN-2135 URL: https://issues.apache.org/jira/browse/YARN-2135 Project: Hadoop YARN

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025581#comment-14025581 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] and [~curino] Me and [~vinodkv]

[jira] [Commented] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

[ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025594#comment-14025594 ] Jian He commented on YARN-2136: --- Given that RMStateStore now is augmented with state machine,

[jira] [Created] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

Jian He created YARN-2136: - Summary: RMStateStore can explicitly handle store/update events when fenced Key: YARN-2136 URL: https://issues.apache.org/jira/browse/YARN-2136 Project: Hadoop YARN

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025599#comment-14025599 ] Jian He commented on YARN-2030: --- Committing this. Filed YARN-2136 for handling events at

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025606#comment-14025606 ] Ray Chiang commented on YARN-1424: -- [~vinodkv] Thanks. I'm still getting used to the

[jira] [Created] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

Sumit Kumar created YARN-2137: - Summary: Add support for logaggregation to a path on non-default filecontext Key: YARN-2137 URL: https://issues.apache.org/jira/browse/YARN-2137 Project: Hadoop YARN

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025626#comment-14025626 ] Jian He commented on YARN-2030: --- Noticed an existing issue that the storedException passed

[jira] [Updated] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Kumar updated YARN-2137: -- Description: Current log-aggregation implementation supports logaggregation to default filecontext

[jira] [Updated] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Kumar updated YARN-2137: -- Attachment: YARN-2137.patch Attaching the patch for review. Add support for logaggregation to a path

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025648#comment-14025648 ] Jian He commented on YARN-2030: --- Opened YARN-2138 for handling un-handled store op failed

[jira] [Created] (YARN-2138) RMStateStore eats store op failed exceptions

Jian He created YARN-2138: - Summary: RMStateStore eats store op failed exceptions Key: YARN-2138 URL: https://issues.apache.org/jira/browse/YARN-2138 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025689#comment-14025689 ] Hadoop QA commented on YARN-2137: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-1424: - Attachment: YARN1424-03.patch From two patches: - Moves dummy ApplicationResourceUsageReport to

[jira] [Commented] (YARN-2138) RMStateStore eats store op failed exceptions

[ https://issues.apache.org/jira/browse/YARN-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025724#comment-14025724 ] Karthik Kambatla commented on YARN-2138:

[jira] [Commented] (YARN-2136) RMStateStore can explicitly handle store/update events when fenced

[ https://issues.apache.org/jira/browse/YARN-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025729#comment-14025729 ] Karthik Kambatla commented on YARN-2136: Adding a FENCED state makes sense to me.

[jira] [Commented] (YARN-2138) RMStateStore eats store op failed exceptions

[ https://issues.apache.org/jira/browse/YARN-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025736#comment-14025736 ] Jian He commented on YARN-2138: --- bq. RMStateStore#notifyStoreOperationFailed handles

[jira] [Commented] (YARN-2138) RMStateStore eats store op failed exceptions

[ https://issues.apache.org/jira/browse/YARN-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025774#comment-14025774 ] Karthik Kambatla commented on YARN-2138: I would suggest working on it here. I can

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025789#comment-14025789 ] Hadoop QA commented on YARN-1424: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2130: - Attachment: YARN-2130.2.patch Cleanup: Adding getRMAppManager, getQueueACLsManager,

[jira] [Updated] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2130: - Attachment: (was: YARN-2130.2.patch) Cleanup: Adding getRMAppManager, getQueueACLsManager,

[jira] [Updated] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2130: - Attachment: YARN-2130.2.patch Cleanup: Adding getRMAppManager, getQueueACLsManager,

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025838#comment-14025838 ] Tsuyoshi OZAWA commented on YARN-2130: -- Updated a patch to address Karthik's comment:

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025903#comment-14025903 ] Tsuyoshi OZAWA commented on YARN-2130: -- The test failure has been filed as YARN-2075,

[jira] [Updated] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2001: -- Attachment: YARN-2001.1.patch Preliminary patch to demonstrate the idea: 1. Add a new timeout config to make

[jira] [Created] (YARN-2139) Add support for disk IO isolation/scheduling for containers

Wei Yan created YARN-2139: - Summary: Add support for disk IO isolation/scheduling for containers Key: YARN-2139 URL: https://issues.apache.org/jira/browse/YARN-2139 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-2140) Add support for network IO isolation/scheduling for containers

Wei Yan created YARN-2140: - Summary: Add support for network IO isolation/scheduling for containers Key: YARN-2140 URL: https://issues.apache.org/jira/browse/YARN-2140 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025959#comment-14025959 ] Karthik Kambatla commented on YARN-1424: Nits: # TestClientRMService has a few

[jira] [Created] (YARN-2141) Resource consumption logging

Carlo Curino created YARN-2141: -- Summary: Resource consumption logging Key: YARN-2141 URL: https://issues.apache.org/jira/browse/YARN-2141 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025983#comment-14025983 ] Tsuyoshi OZAWA commented on YARN-2130: -- Let's do this on this JIRA. I'll update it.

[jira] [Commented] (YARN-2141) Resource consumption logging

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025985#comment-14025985 ] Carlo Curino commented on YARN-2141: This is the product of conversations with

[jira] [Commented] (YARN-2141) Resource consumption logging

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025993#comment-14025993 ] Hitesh Shah commented on YARN-2141: --- Credit to [~gopalv] for the YARN top idea.

[jira] [Updated] (YARN-2138) Cleanup notifyDone* methods in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2138: -- Description: The storedException passed into notifyDoneStoringApplication is always null. Similarly for other

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026005#comment-14026005 ] Hudson commented on YARN-2030: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5672 (See

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026054#comment-14026054 ] haosdent commented on YARN-2140: How to implement this? Cgroup? Add support for network

[jira] [Commented] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026055#comment-14026055 ] Varun Vasudev commented on YARN-2137: - Sumit, have you tested this with the client?

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026080#comment-14026080 ] Jian He commented on YARN-2124: --- Patch looks good overall. Test case: seems just starting RM

[jira] [Commented] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026113#comment-14026113 ] Sumit Kumar commented on YARN-2137: --- [~vvasudev] i tested with the unit test only. if you

[jira] [Commented] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

[ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026116#comment-14026116 ] Varun Vasudev commented on YARN-2137: - No sorry. I should have been more clear.

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026119#comment-14026119 ] Tsuyoshi OZAWA commented on YARN-2130: -- In addition to

[jira] [Updated] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2130: - Attachment: YARN-2130.3.patch Cleanup: Adding getRMAppManager, getQueueACLsManager,

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026130#comment-14026130 ] Yi Tian commented on YARN-2083: --- could anyone review this patch? In fair scheduler, Queue