[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710152#comment-13710152 ] Sandy Ryza commented on YARN-521: - Thanks Bikas! Augment AM - RM client

[jira] [Commented] (YARN-927) Change ContainerRequest to not have more than 1 container count and remove StoreContainerRequest

[ https://issues.apache.org/jira/browse/YARN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710204#comment-13710204 ] Sandy Ryza commented on YARN-927: - I've thought about this a little more and I'm no longer

[jira] [Updated] (YARN-807) When querying apps by queue, iterating over all apps is inefficient and limiting

[ https://issues.apache.org/jira/browse/YARN-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-807: Attachment: YARN-807.patch When querying apps by queue, iterating over all apps is inefficient and

[jira] [Commented] (YARN-927) Change ContainerRequest to not have more than 1 container count and remove StoreContainerRequest

[ https://issues.apache.org/jira/browse/YARN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710388#comment-13710388 ] Sandy Ryza commented on YARN-927: - +1 Change ContainerRequest to not have

[jira] [Created] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

Sandy Ryza created YARN-932: --- Summary: TestResourceLocalizationService.testLocalizationInit can fail on JDK7 Key: YARN-932 URL: https://issues.apache.org/jira/browse/YARN-932 Project: Hadoop YARN

[jira] [Commented] (YARN-932) TestResourceLocalizationService.testLocalizationInit can fail on JDK7

[ https://issues.apache.org/jira/browse/YARN-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710551#comment-13710551 ] Sandy Ryza commented on YARN-932: - {code} org.apache.hadoop.yarn.YarnException:

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708278#comment-13708278 ] Sandy Ryza commented on YARN-521: - Yeah, I noticed. I'm pretty puzzled because I still

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708652#comment-13708652 ] Sandy Ryza commented on YARN-521: - Looks like Eclipse wasn't failing on the non-JUnit

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-6.patch Augment AM - RM client module to be able to request containers only at

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708707#comment-13708707 ] Sandy Ryza commented on YARN-521: - (The diff you were comparing was before I had uploaded

[jira] [Commented] (YARN-927) Change ContainerRequest to not have more than 1 container count and remove StoreContainerRequest

[ https://issues.apache.org/jira/browse/YARN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13709359#comment-13709359 ] Sandy Ryza commented on YARN-927: - Removing the ability to request multiple containers would

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708202#comment-13708202 ] Sandy Ryza commented on YARN-521: - Feel free to make changes to the doc. You are correct

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-4.patch Augment AM - RM client module to be able to request containers only at

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-4.patch Augment AM - RM client module to be able to request containers only at

[jira] [Commented] (YARN-912) Create exceptions package in common/api for yarn and move client facing exceptions to them

[ https://issues.apache.org/jira/browse/YARN-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707340#comment-13707340 ] Sandy Ryza commented on YARN-912: - +1 to the doc changes. I still think we should move the

[jira] [Commented] (YARN-912) Create exceptions package in common/api for yarn and move client facing exceptions to them

[ https://issues.apache.org/jira/browse/YARN-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707362#comment-13707362 ] Sandy Ryza commented on YARN-912: - bq. Sandy, what do you mean by client.api? Which client?

[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application

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

[jira] [Updated] (YARN-333) Schedulers cannot control the queue-name of an application

[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-333: Attachment: YARN-333-3.patch Schedulers cannot control the queue-name of an application

[jira] [Commented] (YARN-912) Create exceptions package in common/api for yarn and move client facing exceptions to them

[ https://issues.apache.org/jira/browse/YARN-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706273#comment-13706273 ] Sandy Ryza commented on YARN-912: - Does it really make sense to put exceptions in their own

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13705341#comment-13705341 ] Sandy Ryza commented on YARN-521: - bq. Shouldnt this also check that the inferred rack1 has

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

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

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-3.patch Augment AM - RM client module to be able to request containers only at

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-2.patch Augment AM - RM client module to be able to request containers only at

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: (was: YARN-521-2.patch) Augment AM - RM client module to be able to request containers

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-2.patch Augment AM - RM client module to be able to request containers only at

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-2.patch Augment AM - RM client module to be able to request containers only at

[jira] [Updated] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-649: Attachment: YARN-649-5.patch Make container logs available over HTTP in plain text

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703629#comment-13703629 ] Sandy Ryza commented on YARN-649: - Updated patch removes the JSON option and adds javadoc

[jira] [Commented] (YARN-908) URL is a YARN API record instead of being java.net.url

[ https://issues.apache.org/jira/browse/YARN-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703798#comment-13703798 ] Sandy Ryza commented on YARN-908: - Looks like the idea was to make it protobuf-serializable?

[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-7.patch Add a tracing async dispatcher to simplify debugging

[jira] [Updated] (YARN-910) Allow auxiliary services to listen for container starts and completions

[ https://issues.apache.org/jira/browse/YARN-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-910: Description: Making container start and completion events available to auxiliary services would allow them

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-1.patch Augment AM - RM client module to be able to request containers only at

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702424#comment-13702424 ] Sandy Ryza commented on YARN-521: - I uploaded a new patch that adds in the checks mentioned

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-8.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702427#comment-13702427 ] Sandy Ryza commented on YARN-791: - Uploaded a patch that updates the CLI documentation.

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702565#comment-13702565 ] Sandy Ryza commented on YARN-791: - Thanks Vinod! I initially tried something similar to

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702595#comment-13702595 ] Sandy Ryza commented on YARN-791: - Totally agree. Filed YARN-905 and we can figure out the

[jira] [Created] (YARN-905) Add state filters to nodes CLI

Sandy Ryza created YARN-905: --- Summary: Add state filters to nodes CLI Key: YARN-905 URL: https://issues.apache.org/jira/browse/YARN-905 Project: Hadoop YARN Issue Type: Improvement Affects

[jira] [Updated] (YARN-905) Add state filters to nodes CLI

[ https://issues.apache.org/jira/browse/YARN-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-905: Assignee: (was: Sandy Ryza) Add state filters to nodes CLI --

[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=13702689#comment-13702689 ] Sandy Ryza commented on YARN-366: - Rebased onto trunk again Add a tracing

[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-6.patch Add a tracing async dispatcher to simplify debugging

[jira] [Commented] (YARN-902) Used Resources field in Resourcemanager scheduler UI not displaying any values

[ https://issues.apache.org/jira/browse/YARN-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700466#comment-13700466 ] Sandy Ryza commented on YARN-902: - [~nishan], which scheduler is this occurring for you

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521.patch Augment AM - RM client module to be able to request containers only at

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699346#comment-13699346 ] Sandy Ryza commented on YARN-791: - Chatted with Vinod about this offline. The thinking is

[jira] [Created] (YARN-899) Get queue administration ACLs working

Sandy Ryza created YARN-899: --- Summary: Get queue administration ACLs working Key: YARN-899 URL: https://issues.apache.org/jira/browse/YARN-899 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-7.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699455#comment-13699455 ] Sandy Ryza commented on YARN-791: - Uploaded patch that makes the discussed changes. I had a

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13699497#comment-13699497 ] Sandy Ryza commented on YARN-675: - Would there be an issue with including the AM container

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13698444#comment-13698444 ] Sandy Ryza commented on YARN-649: - Thanks for taking a look Zhijie. bq. why does getLogs

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13697209#comment-13697209 ] Sandy Ryza commented on YARN-675: - [~zjshen], thanks for the help, feel free to take it

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-5.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-5.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: (was: YARN-791-5.patch) Ensure that RM RPC APIs that return nodes are consistent with

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-6.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695663#comment-13695663 ] Sandy Ryza commented on YARN-883: - Thanks, just filed YARN-889 Expose Fair

[jira] [Created] (YARN-889) Make bars in Fair Scheduler web UI show multiple resources

Sandy Ryza created YARN-889: --- Summary: Make bars in Fair Scheduler web UI show multiple resources Key: YARN-889 URL: https://issues.apache.org/jira/browse/YARN-889 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-461) Fair scheduler accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695675#comment-13695675 ] Sandy Ryza commented on YARN-461: - Per Arun's suggestion, we don't need to make changes to

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694426#comment-13694426 ] Sandy Ryza commented on YARN-883: - Test failure is unrelated. Updated patch should fix

[jira] [Updated] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-883: Attachment: YARN-883-1.patch Expose Fair Scheduler-specific queue metrics

[jira] [Updated] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-649: Attachment: YARN-649-4.patch Make container logs available over HTTP in plain text

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692224#comment-13692224 ] Sandy Ryza commented on YARN-881: - There are places in the code that rely on the current

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692436#comment-13692436 ] Sandy Ryza commented on YARN-883: - Submitted patch that adds an FSQueueMetrics, which

[jira] [Updated] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-883: Attachment: YARN-883.patch Expose Fair Scheduler-specific queue metrics

[jira] [Moved] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza moved MAPREDUCE-5350 to YARN-883: Component/s: (was: scheduler) scheduler

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692501#comment-13692501 ] Sandy Ryza commented on YARN-649: - Uploading a patch that takes Vinod's comments into

[jira] [Updated] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-649: Attachment: YARN-649-3.patch Make container logs available over HTTP in plain text

[jira] [Updated] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-883: Attachment: YARN-883-1.patch Expose Fair Scheduler-specific queue metrics

[jira] [Resolved] (YARN-758) Fair scheduler has some bug that causes TestRMRestart to fail

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-758. - Resolution: Not A Problem Fair scheduler has some bug that causes TestRMRestart to fail

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692666#comment-13692666 ] Sandy Ryza commented on YARN-763: - Can we move all of this into the switch statement,

[jira] [Commented] (YARN-827) Need to make Resource arithmetic methods accessible

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690844#comment-13690844 ] Sandy Ryza commented on YARN-827: - In trunk (at least) it looks like the original classes in

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

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

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

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-736: Attachment: YARN-736-4.patch Add a multi-resource fair sharing metric

[jira] [Resolved] (YARN-827) Need to make Resource arithmetic methods accessible

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-827. - Resolution: Fixed Need to make Resource arithmetic methods accessible

[jira] [Commented] (YARN-827) Need to make Resource arithmetic methods accessible

[ https://issues.apache.org/jira/browse/YARN-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690885#comment-13690885 ] Sandy Ryza commented on YARN-827: - Thanks Bikas! Marking this as resolved again.

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

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13690898#comment-13690898 ] Sandy Ryza commented on YARN-736: - The test failure appears unrelated. I get also get it

[jira] [Commented] (YARN-866) Add test for class ResourceWeights

[ https://issues.apache.org/jira/browse/YARN-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689712#comment-13689712 ] Sandy Ryza commented on YARN-866: - Wei, the patch looks good. My only nit is that two

[jira] [Commented] (YARN-866) Add test for class ResourceWeights

[ https://issues.apache.org/jira/browse/YARN-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689755#comment-13689755 ] Sandy Ryza commented on YARN-866: - +1 Add test for class ResourceWeights

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-4.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687802#comment-13687802 ] Sandy Ryza commented on YARN-791: - Attaching patch that makes both the REST API and the RPC

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

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688204#comment-13688204 ] Sandy Ryza commented on YARN-736: - All the FakeSchedulable constructors appear to be used.

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

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-736: Attachment: YARN-736-3.patch Add a multi-resource fair sharing metric

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688500#comment-13688500 ] Sandy Ryza commented on YARN-791: - [~vinodkv], does Alejandro's suggestion seem acceptable

[jira] [Updated] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-858: Summary: Move Resources and the calculators to a new package util.resource in yarn-common (was: Move

[jira] [Commented] (YARN-858) Move Resources and the calculators to a new package util.resource in yarn-common

[ https://issues.apache.org/jira/browse/YARN-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688664#comment-13688664 ] Sandy Ryza commented on YARN-858: - The JIRA description says for userland use, but the

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687443#comment-13687443 ] Sandy Ryza commented on YARN-791: - I'll work on a patch for multiple states.

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685013#comment-13685013 ] Sandy Ryza commented on YARN-791: - [~hitesh], the /nodes REST API returns all RUNNING and

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685023#comment-13685023 ] Sandy Ryza commented on YARN-791: - [~vinodkv], my concern about a single static factory in

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685025#comment-13685025 ] Sandy Ryza commented on YARN-791: - bq. was that giving a node and setting all states to true

[jira] [Commented] (YARN-588) Two identical utility methods in different classes to build Resource

[ https://issues.apache.org/jira/browse/YARN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685028#comment-13685028 ] Sandy Ryza commented on YARN-588: - +1, LGTM Two identical utility methods

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-2.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686075#comment-13686075 ] Sandy Ryza commented on YARN-791: - So apparently, with protobufs, you can not have a default

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686292#comment-13686292 ] Sandy Ryza commented on YARN-791: - I suggested this on YARN-791, but others didn't think it

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686296#comment-13686296 ] Sandy Ryza commented on YARN-791: - suggested this on YARN-642 I mean

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

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-736: Attachment: YARN-736-2.patch Add a multi-resource fair sharing metric

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684785#comment-13684785 ] Sandy Ryza commented on YARN-387: - I have a couple comments on this. I have father's day

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684836#comment-13684836 ] Sandy Ryza commented on YARN-387: - ApplicationClientProtocol - There are uses of this

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684839#comment-13684839 ] Sandy Ryza commented on YARN-779: - Ah, I misunderstood how removeContainerRequest works.

[jira] [Commented] (YARN-387) Fix inconsistent protocol naming

[ https://issues.apache.org/jira/browse/YARN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684886#comment-13684886 ] Sandy Ryza commented on YARN-387: - I like ContainerManagementProtocol too. Maybe

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684249#comment-13684249 ] Sandy Ryza commented on YARN-779: - [~maysamyabandeh], I follow you until the end. What API

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684413#comment-13684413 ] Sandy Ryza commented on YARN-779: - The MR AM has solved this problem purely on the AM side

<    5   6   7   8   9   10   11   12   13   14   >