[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673526#comment-13673526 ] Sandy Ryza commented on YARN-752: - Cool, I think that option is the best too. Updated the

[jira] [Updated] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-752: Description: A ContainerRequest that includes node-level requests must also include matching rack-level

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673577#comment-13673577 ] Sandy Ryza commented on YARN-752: - [~bikassaha], do you have an opinion on whether it makes

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673677#comment-13673677 ] Sandy Ryza commented on YARN-642: - [~vinodkv], is the latest patch satisfactory to you?

[jira] [Updated] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-752: Attachment: YARN-752.patch In AMRMClient, automatically add corresponding rack requests for requested

[jira] [Commented] (YARN-752) In AMRMClient, automatically add corresponding rack requests for requested nodes

[ https://issues.apache.org/jira/browse/YARN-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673859#comment-13673859 ] Sandy Ryza commented on YARN-752: - Attached a patch that resolves racks in the AMRMClient

[jira] [Commented] (YARN-749) Rename ResourceRequest (get,set)HostName to (get,set)ResourceName

[ https://issues.apache.org/jira/browse/YARN-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672636#comment-13672636 ] Sandy Ryza commented on YARN-749: - +1, have thought this would be a good change for a while.

[jira] [Created] (YARN-752) Throw exception if AMRMClient.ContainerRequest is given invalid locations

Sandy Ryza created YARN-752: --- Summary: Throw exception if AMRMClient.ContainerRequest is given invalid locations Key: YARN-752 URL: https://issues.apache.org/jira/browse/YARN-752 Project: Hadoop YARN

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671738#comment-13671738 ] Sandy Ryza commented on YARN-326: - Attached a rebased patch Add

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Labels: incompatible (was: ) Add multi-resource scheduling to the fair scheduler

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326-7.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671862#comment-13671862 ] Sandy Ryza commented on YARN-326: - Uploaded a patch that addresses Alejandro's comments

[jira] [Created] (YARN-736) Add a multi-resource fair sharing metric

Sandy Ryza created YARN-736: --- Summary: Add a multi-resource fair sharing metric Key: YARN-736 URL: https://issues.apache.org/jira/browse/YARN-736 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326-5.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670991#comment-13670991 ] Sandy Ryza commented on YARN-326: - Uploaded a patch that addresses Karthik's comments and

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326-3.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669403#comment-13669403 ] Sandy Ryza commented on YARN-326: - Uploading a new patch that implements DRF comparisons

[jira] [Updated] (YARN-656) In scheduler UI, including reserved memory in Memory Total can make it exceed cluster capacity.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-656: Attachment: YARN-656.patch In scheduler UI, including reserved memory in Memory Total can make it

[jira] [Commented] (YARN-512) Log aggregation root directory check is more expensive than it needs to be

[ https://issues.apache.org/jira/browse/YARN-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669650#comment-13669650 ] Sandy Ryza commented on YARN-512: - [~tucu00] and I talked about this when working on

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326-4.patch Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668508#comment-13668508 ] Sandy Ryza commented on YARN-578: - Thanks [~ojoshi], looks good to me now.

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668669#comment-13668669 ] Sandy Ryza commented on YARN-392: - [~bikassaha], thanks for taking the time to iterate on

[jira] [Commented] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666440#comment-13666440 ] Sandy Ryza commented on YARN-578: - Hi Omkar. The patch is looking good. A couple nits: *

[jira] [Updated] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Target Version/s: 2.0.5-beta Flatten NodeReport -- Key: YARN-686

[jira] [Updated] (YARN-686) Flatten NodeStatus

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Summary: Flatten NodeStatus (was: Flatten NodeReport) Flatten NodeStatus --

[jira] [Updated] (YARN-686) Flatten NodeStatus

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Description: The NodeStatus returned by getClusterNodes or given to AMs in heartbeat responses includes both

[jira] [Created] (YARN-725) NodeStatus is missing audience and stability annotations

Sandy Ryza created YARN-725: --- Summary: NodeStatus is missing audience and stability annotations Key: YARN-725 URL: https://issues.apache.org/jira/browse/YARN-725 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Summary: Flatten NodeReport (was: Flatten NodeStatus) Flatten NodeReport --

[jira] [Updated] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Description: The NodeReport returned by getClusterNodes or given to AMs in heartbeat responses includes both

[jira] [Updated] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-8.patch Make it possible to specify hard locality constraints in resource requests

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665465#comment-13665465 ] Sandy Ryza commented on YARN-392: - Uploaded a patch that addresses Bikas's latest comments.

[jira] [Commented] (YARN-711) Copy BuilderUtil methods into individual records

[ https://issues.apache.org/jira/browse/YARN-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663275#comment-13663275 ] Sandy Ryza commented on YARN-711: - +1`to this Copy BuilderUtil methods

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663309#comment-13663309 ] Sandy Ryza commented on YARN-392: - bq. We mean to that level and beyond? You're right. I'll

[jira] [Updated] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-7.patch Make it possible to specify hard locality constraints in resource requests

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663453#comment-13663453 ] Sandy Ryza commented on YARN-392: - Uploaded a new patch to address Bikas' comments.

[jira] [Created] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf

Sandy Ryza created YARN-702: --- Summary: minicluster classpath construction requires user to set yarn.is.minicluster in the job conf Key: YARN-702 URL: https://issues.apache.org/jira/browse/YARN-702 Project:

[jira] [Updated] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf

[ https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-702: Assignee: Sandy Ryza minicluster classpath construction requires user to set yarn.is.minicluster in

[jira] [Commented] (YARN-702) minicluster classpath construction requires user to set yarn.is.minicluster in the job conf

[ https://issues.apache.org/jira/browse/YARN-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662256#comment-13662256 ] Sandy Ryza commented on YARN-702: - In the past couple weeks, I've had two different people

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662302#comment-13662302 ] Sandy Ryza commented on YARN-392: - The crisp definition I had in mind was: if

[jira] [Updated] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-5.patch Make it possible to specify hard locality constraints in resource requests

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662382#comment-13662382 ] Sandy Ryza commented on YARN-392: - Uploaded a patch that takes away node-level blacklisting

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662435#comment-13662435 ] Sandy Ryza commented on YARN-392: - Weird, those tests passed locally for me. Will look into

[jira] [Updated] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-6.patch Make it possible to specify hard locality constraints in resource requests

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662493#comment-13662493 ] Sandy Ryza commented on YARN-392: - Looks like I hadn't rebased like I thought I had.

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661705#comment-13661705 ] Sandy Ryza commented on YARN-392: - As I mentioned, any mechanism that allows whitelisting

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661767#comment-13661767 ] Sandy Ryza commented on YARN-392: - We currently have a working patch that has gone through

[jira] [Commented] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661403#comment-13661403 ] Sandy Ryza commented on YARN-392: - bq. it would still be possible to blacklist racks by

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660946#comment-13660946 ] Sandy Ryza commented on YARN-392: - We are implementing the approach outlined by Arun in his

[jira] [Updated] (YARN-392) Make it possible to specify hard locality constraints in resource requests

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Summary: Make it possible to specify hard locality constraints in resource requests (was: Make it possible

[jira] [Commented] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

[ https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661052#comment-13661052 ] Sandy Ryza commented on YARN-696: - In YARN-642, we're addressing a similar issue with the

[jira] [Commented] (YARN-689) Add multiplier unit to resourcecapabilities

[ https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661159#comment-13661159 ] Sandy Ryza commented on YARN-689: - Consider this situation: All the nodes in a cluster have

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660345#comment-13660345 ] Sandy Ryza commented on YARN-392: - It would mean Don't give me a container at this priority

[jira] [Created] (YARN-686) Flatten NodeReport

Sandy Ryza created YARN-686: --- Summary: Flatten NodeReport Key: YARN-686 URL: https://issues.apache.org/jira/browse/YARN-686 Project: Hadoop YARN Issue Type: Sub-task Components: api

[jira] [Updated] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Description: The NodeReport returned by getClusterNodes or given to AMs in heartbeat responses includes both

[jira] [Updated] (YARN-686) Flatten NodeReport

[ https://issues.apache.org/jira/browse/YARN-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-686: Description: The NodeReport returned by getClusterNodes or given to AMs in heartbeat responses includes

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658836#comment-13658836 ] Sandy Ryza commented on YARN-366: - Uploading a patch to address the findbugs warnings.

[jira] [Updated] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-366: Attachment: YARN-366-4.patch Add a tracing async dispatcher to simplify debugging

[jira] [Updated] (YARN-656) In scheduler UI, including reserved memory in Memory Total can make it exceed cluster capacity.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-656: Summary: In scheduler UI, including reserved memory in Memory Total can make it exceed cluster capacity.

[jira] [Updated] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642-2.patch Fix up /nodes REST API to have 1 param and be consistent with the Java API

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657393#comment-13657393 ] Sandy Ryza commented on YARN-642: - Latest patch should fix failing test

[jira] [Updated] (YARN-664) throw InvalidRequestException for requests with different capabilities at the same priority

[ https://issues.apache.org/jira/browse/YARN-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-664: Description: Nothing stops an application from submitting a request with priority=1, location=*, memory=1024

[jira] [Commented] (YARN-664) throw InvalidRequestException for requests with different capabilities at the same priority

[ https://issues.apache.org/jira/browse/YARN-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657452#comment-13657452 ] Sandy Ryza commented on YARN-664: - My mistake - the original example was valid, just

[jira] [Commented] (YARN-664) throw InvalidRequestException for requests with different capabilities at the same priority

[ https://issues.apache.org/jira/browse/YARN-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657453#comment-13657453 ] Sandy Ryza commented on YARN-664: - Sorry, [~acm], meant to mention [~acmurthy], not you.

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-4.patch Make it possible to schedule to specific nodes without dropping locality

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657504#comment-13657504 ] Sandy Ryza commented on YARN-392: - Updated patch adds javadocs Make it

[jira] [Resolved] (YARN-350) FSSchedulerNode is always instantiated with a 0 virtual core capacity

[ https://issues.apache.org/jira/browse/YARN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-350. - Resolution: Duplicate FSSchedulerNode is always instantiated with a 0 virtual core capacity

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657842#comment-13657842 ] Sandy Ryza commented on YARN-366: - That seems reasonable to me, Vinod. Uploading a patch

[jira] [Updated] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-366: Attachment: YARN-366-3.patch Add a tracing async dispatcher to simplify debugging

[jira] [Commented] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656582#comment-13656582 ] Sandy Ryza commented on YARN-642: - [~vinodkv], your proposal sounds good to me. Uploading a

[jira] [Updated] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642-2.patch Fix up /nodes REST API to have 1 param and be consistent with the Java API

[jira] [Updated] (YARN-656) In scheduler UI, including reserved memory Memory Total can make it exceed cluster capacity.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-656: Summary: In scheduler UI, including reserved memory Memory Total can make it exceed cluster capacity. (was:

[jira] [Created] (YARN-675) In YarnClient, pull AM logs on AM container failure

Sandy Ryza created YARN-675: --- Summary: In YarnClient, pull AM logs on AM container failure Key: YARN-675 URL: https://issues.apache.org/jira/browse/YARN-675 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-499) On container failure, surface logs to client

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655619#comment-13655619 ] Sandy Ryza commented on YARN-499: - bq. So that answers it? Yeah, it does. Thanks Vinod. bq.

[jira] [Resolved] (YARN-499) On container failure, surface logs to client

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-499. - Resolution: Won't Fix On container failure, surface logs to client

[jira] [Updated] (YARN-499) On container failure, include logs in diagnostics

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-499: Summary: On container failure, include logs in diagnostics (was: On container failure, surface logs to

[jira] [Updated] (YARN-675) In YarnClient, pull AM logs on AM container failure

[ https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-675: Description: Similar to MAPREDUCE-4362, when an AM container fails, it would be helpful to pull its logs

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13654708#comment-13654708 ] Sandy Ryza commented on YARN-392: - I think the server should check weird requests and state.

[jira] [Created] (YARN-664) throw InvalidRequestException for requests with different capabilities at the same priority

Sandy Ryza created YARN-664: --- Summary: throw InvalidRequestException for requests with different capabilities at the same priority Key: YARN-664 URL: https://issues.apache.org/jira/browse/YARN-664 Project:

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-3.patch Make it possible to schedule to specific nodes without dropping locality

[jira] [Commented] (YARN-642) Fix up RMWebServices#getNodes

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13655089#comment-13655089 ] Sandy Ryza commented on YARN-642: - bq. A general suggestion: Please add a little more

[jira] [Updated] (YARN-642) Fix up /nodes REST API to remove unnecessary param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Summary: Fix up /nodes REST API to remove unnecessary param and be consistent with the Java API (was: Fix

[jira] [Updated] (YARN-642) Fix up /nodes REST API to have 1 param and be consistent with the Java API

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Summary: Fix up /nodes REST API to have 1 param and be consistent with the Java API (was: Fix up /nodes

[jira] [Updated] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-392: Attachment: YARN-392-2.patch Make it possible to schedule to specific nodes without dropping locality

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653195#comment-13653195 ] Sandy Ryza commented on YARN-392: - Disable-node allows you to say I specifically don't want

[jira] [Updated] (YARN-642) Fix up RMWebServices#getNodes

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642.patch Fix up RMWebServices#getNodes -

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653390#comment-13653390 ] Sandy Ryza commented on YARN-392: - bq. Looks like this will be blocked by YARN-394. The APIs

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653438#comment-13653438 ] Sandy Ryza commented on YARN-392: - bq. The AMRMClient APIs should be added to ensure that

[jira] [Commented] (YARN-642) Fix up RMWebServices#getNodes

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653475#comment-13653475 ] Sandy Ryza commented on YARN-642: - Attaching a new patch that makes those changes

[jira] [Updated] (YARN-642) Fix up RMWebServices#getNodes

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Attachment: YARN-642-1.patch Fix up RMWebServices#getNodes -

[jira] [Commented] (YARN-656) In scheduler UI, Memory Total should not include reserved memory.

[ https://issues.apache.org/jira/browse/YARN-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652107#comment-13652107 ] Sandy Ryza commented on YARN-656: - Agreed that memory total should be the total amount of

[jira] [Updated] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

[ https://issues.apache.org/jira/browse/YARN-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-655: Attachment: YARN-655.patch Fair scheduler metrics should subtract allocated memory from available

[jira] [Commented] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

[ https://issues.apache.org/jira/browse/YARN-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652186#comment-13652186 ] Sandy Ryza commented on YARN-655: - Uploaded patch that subtracts allocated memory from

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-568: Attachment: YARN-568-2.patch FairScheduler: support for work-preserving preemption

[jira] [Commented] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651440#comment-13651440 ] Sandy Ryza commented on YARN-568: - Posted a patch that adds kill previously listed

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-568: Attachment: YARN-568-2.patch FairScheduler: support for work-preserving preemption

[jira] [Commented] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13651457#comment-13651457 ] Sandy Ryza commented on YARN-568: - Updated patch should fix findbugs warning

[jira] [Created] (YARN-655) Fair scheduler metrics should subtract allocated memory from available memory

Sandy Ryza created YARN-655: --- Summary: Fair scheduler metrics should subtract allocated memory from available memory Key: YARN-655 URL: https://issues.apache.org/jira/browse/YARN-655 Project: Hadoop YARN

[jira] [Created] (YARN-656) In scheduler UI, Memory Total should not include reserved memory.

Sandy Ryza created YARN-656: --- Summary: In scheduler UI, Memory Total should not include reserved memory. Key: YARN-656 URL: https://issues.apache.org/jira/browse/YARN-656 Project: Hadoop YARN

[jira] [Created] (YARN-657) Fair scheduler can consider apps starved when they are alone on the cluster

Sandy Ryza created YARN-657: --- Summary: Fair scheduler can consider apps starved when they are alone on the cluster Key: YARN-657 URL: https://issues.apache.org/jira/browse/YARN-657 Project: Hadoop YARN

[jira] [Commented] (YARN-646) Some issues in Fair Scheduler's document

[ https://issues.apache.org/jira/browse/YARN-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649849#comment-13649849 ] Sandy Ryza commented on YARN-646: - +1, thanks for fixing these Some issues

<    7   8   9   10   11   12   13   14   15   16   >