[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888.007.patch Fixing failed TestCase and some of the checkstyle warnings. >

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888.005.patch > Corrective mechanisms for rebalancing NM container queues >

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273104#comment-15273104 ] Arun Suresh commented on YARN-2888: --- Thanks for the review [~kkaranasos]. I agree with most of your

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888.006.patch Thank you [~curino] for the detailed review.. apologize for the delay in

[jira] [Commented] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269086#comment-15269086 ] Arun Suresh commented on YARN-5035: --- [~kasha], You think it is possible to generalize this further ? I

[jira] [Created] (YARN-5059) Changes to AbstractYarnScheduler to incorporate the Bundler

Arun Suresh created YARN-5059: - Summary: Changes to AbstractYarnScheduler to incorporate the Bundler Key: YARN-5059 URL: https://issues.apache.org/jira/browse/YARN-5059 Project: Hadoop YARN

[jira] [Created] (YARN-5060) Changes to Fair Scheduler to incorporate Bundler

Arun Suresh created YARN-5060: - Summary: Changes to Fair Scheduler to incorporate Bundler Key: YARN-5060 URL: https://issues.apache.org/jira/browse/YARN-5060 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-5058) Expose Bundler logic and API as general purpose utility

[ https://issues.apache.org/jira/browse/YARN-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5058: -- Summary: Expose Bundler logic and API as general purpose utility (was: Expose Bundler and API as

[jira] [Created] (YARN-5061) Changes to Capacity Scheduler to incorporate Bundler

Arun Suresh created YARN-5061: - Summary: Changes to Capacity Scheduler to incorporate Bundler Key: YARN-5061 URL: https://issues.apache.org/jira/browse/YARN-5061 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-5058) Expose Bundler logic and API as general purpose utility

[ https://issues.apache.org/jira/browse/YARN-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-5058: - Assignee: Arun Suresh > Expose Bundler logic and API as general purpose utility >

[jira] [Created] (YARN-5058) Expose Bundler and API as general utility

Arun Suresh created YARN-5058: - Summary: Expose Bundler and API as general utility Key: YARN-5058 URL: https://issues.apache.org/jira/browse/YARN-5058 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-4902) [Umbrella] Generalized and unified scheduling-strategies in YARN

[ https://issues.apache.org/jira/browse/YARN-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241673#comment-15241673 ] Arun Suresh commented on YARN-4902: --- It is somewhat similar, i agree... But, I was hoping to decouple the

[jira] [Updated] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2883: -- Attachment: YARN-2883.013.patch Looks like Jenkins is complaining because of the string 'trunk' in the

[jira] [Commented] (YARN-4468) Document the general ReservationSystem functionality, and the REST API

[ https://issues.apache.org/jira/browse/YARN-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243877#comment-15243877 ] Arun Suresh commented on YARN-4468: --- +1, Committing this shortly > Document the general

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243722#comment-15243722 ] Arun Suresh commented on YARN-2883: --- Looks like you have to add an additional {noformat} if (!event

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246283#comment-15246283 ] Arun Suresh commented on YARN-2883: --- [~kasha], bq. As I said, for the config, I am comfortable filing a

[jira] [Created] (YARN-4972) Cleanup QueuingContainerManager tests to remove long sleep times

Arun Suresh created YARN-4972: - Summary: Cleanup QueuingContainerManager tests to remove long sleep times Key: YARN-4972 URL: https://issues.apache.org/jira/browse/YARN-4972 Project: Hadoop YARN

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250189#comment-15250189 ] Arun Suresh commented on YARN-2883: --- Filed YARN-4972 to fix the test cases. Thanks for the review

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15241460#comment-15241460 ] Arun Suresh commented on YARN-2883: --- Looks like jenkins did not pick up the latest patch.. just kicked

[jira] [Commented] (YARN-4468) Document the general ReservationSystem functionality, and the REST API

[ https://issues.apache.org/jira/browse/YARN-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239842#comment-15239842 ] Arun Suresh commented on YARN-4468: --- [~curino]/[~subru], The patch itself looks good... but it looks like

[jira] [Updated] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2883: -- Attachment: YARN-2883-trunk.013.patch Updating patch to fix some compilation issues.. > Queuing of

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.010.patch Hmm.. Being a test class, I did not want to modify any more of it than

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393230#comment-15393230 ] Arun Suresh commented on YARN-5392: --- The remaining checkstyles are all related to method parameters /

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Summary: Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerRequestKey

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394580#comment-15394580 ] Arun Suresh commented on YARN-5392: --- The test failure is unrelated > Replace use of Priority in the

[jira] [Commented] (YARN-5351) ResourceRequest should take ExecutionType into account during comparison

[ https://issues.apache.org/jira/browse/YARN-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394930#comment-15394930 ] Arun Suresh commented on YARN-5351: --- +1, Committing this shortly > ResourceRequest should take

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391356#comment-15391356 ] Arun Suresh commented on YARN-5392: --- Thanks for taking a look [~kasha], bq. The name is very

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.009.patch Updating patch based on [~kasha]'s suggestions. Based on offline

[jira] [Assigned] (YARN-4889) Changes in AMRMClient for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-4889: - Assignee: Arun Suresh (was: Subru Krishnan) > Changes in AMRMClient for identifying

[jira] [Commented] (YARN-4889) Changes in AMRMClient for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396268#comment-15396268 ] Arun Suresh commented on YARN-4889: --- Taking this over from [~subru] > Changes in AMRMClient for

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390355#comment-15390355 ] Arun Suresh commented on YARN-5392: --- thanks [~leftnoteasy] .. will do > Replace use of Priority in the

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.007.patch Thanks for the review [~leftnoteasy] Updating the patch with you

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.008.patch Fixing test cases.. > Replace use of Priority in the Scheduling

[jira] [Commented] (YARN-4888) Changes in RM container allocation for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399430#comment-15399430 ] Arun Suresh commented on YARN-4888: --- [~subru], I see just a few minor nits: # I feel the *UNDEFINED*

[jira] [Commented] (YARN-5113) Refactoring and other clean-up for distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1545#comment-1545 ] Arun Suresh commented on YARN-5113: --- Thanks [~kkaranasos], Couple of nits: # Since we are refactoring,

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400228#comment-15400228 ] Arun Suresh commented on YARN-5221: --- ping.. [~subru], [~kasha], [~leftnoteasy]... > Expose

[jira] [Commented] (YARN-4888) Changes in RM container allocation for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400563#comment-15400563 ] Arun Suresh commented on YARN-4888: --- Lets also add a testcase (possibly a TestSchedulerRequestKey) to

[jira] [Created] (YARN-5457) Refactor DistributedScheduling framework to pull out common functionality

Arun Suresh created YARN-5457: - Summary: Refactor DistributedScheduling framework to pull out common functionality Key: YARN-5457 URL: https://issues.apache.org/jira/browse/YARN-5457 Project: Hadoop YARN

[jira] [Updated] (YARN-5457) Refactor DistributedScheduling framework to pull out common functionality

[ https://issues.apache.org/jira/browse/YARN-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5457: -- Description: Opening this JIRA to track the following refactoring missed in YARN-5113: was: Opening

[jira] [Updated] (YARN-5457) Refactor DistributedScheduling framework to pull out common functionality

[ https://issues.apache.org/jira/browse/YARN-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5457: -- Assignee: Konstantinos Karanasos > Refactor DistributedScheduling framework to pull out common

[jira] [Updated] (YARN-5457) Refactor DistributedScheduling framework to pull out common functionality

[ https://issues.apache.org/jira/browse/YARN-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5457: -- Description: Opening this JIRA to track the some refactoring missed in YARN-5113: was: Opening this

[jira] [Commented] (YARN-5457) Refactor DistributedScheduling framework to pull out common functionality

[ https://issues.apache.org/jira/browse/YARN-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401306#comment-15401306 ] Arun Suresh commented on YARN-5457: --- I propose the following changes : * Move

[jira] [Commented] (YARN-5113) Refactoring and other clean-up for distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401295#comment-15401295 ] Arun Suresh commented on YARN-5113: --- +1, Committing this shortly (will fix the indentation check-style

[jira] [Commented] (YARN-5441) Fixing minor Scheduler test case failures

[ https://issues.apache.org/jira/browse/YARN-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396685#comment-15396685 ] Arun Suresh commented on YARN-5441: --- Thanks for raising this [~subru]. +1 Please also verify this fixes

[jira] [Updated] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5221: -- Attachment: YARN-5221.008.patch Rebasing patch against trunk. [~leftnoteasy], regarding your comment,

[jira] [Commented] (YARN-4888) Changes in RM container allocation for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402921#comment-15402921 ] Arun Suresh commented on YARN-4888: --- Thanks for updating [~subru] +1 for the latest patch (pending

[jira] [Commented] (YARN-4602) Simple and Scalable Message Service for YARN application

[ https://issues.apache.org/jira/browse/YARN-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405770#comment-15405770 ] Arun Suresh commented on YARN-4602: --- [~djp], wondering if you've taken a look at apache REEF. It uses an

[jira] [Created] (YARN-5501) Container Pooling in YARN

Arun Suresh created YARN-5501: - Summary: Container Pooling in YARN Key: YARN-5501 URL: https://issues.apache.org/jira/browse/YARN-5501 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-5486) Update OpportunisticContainerAllocatorAMService::allocate method to handle OPPORTUNISTIC container requests

[ https://issues.apache.org/jira/browse/YARN-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5486: -- Summary: Update OpportunisticContainerAllocatorAMService::allocate method to handle OPPORTUNISTIC

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406049#comment-15406049 ] Arun Suresh commented on YARN-5079: --- We were going thru SLIDER-787. With regard to the state of slider as

[jira] [Updated] (YARN-4889) Changes in AMRMClient for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4889: -- Attachment: YARN-4889.002.patch Updating patch with some tests... > Changes in AMRMClient for

[jira] [Commented] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375866#comment-15375866 ] Arun Suresh commented on YARN-5181: --- Thanks for the patch [~kasha] Some minor comments: # Remove the

[jira] [Commented] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376380#comment-15376380 ] Arun Suresh commented on YARN-4888: --- Thanks for the patch [~subru] Couple of initial comments: # In

[jira] [Comment Edited] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376380#comment-15376380 ] Arun Suresh edited comment on YARN-4888 at 7/14/16 6:12 AM: Thanks for the

[jira] [Resolved] (YARN-2895) Integrate distributed scheduling with capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-2895. --- Resolution: Duplicate Marking this as Duplicate as YARN-5220 will subsume this. Additionally, it seeks

[jira] [Updated] (YARN-4503) Allow for a pluggable policy to decide if a ResourceRequest is GUARANTEED or not

[ https://issues.apache.org/jira/browse/YARN-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4503: -- Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-4742) > Allow for a pluggable

[jira] [Commented] (YARN-5414) Integrate NodeQueueLoadMonitor with ClusterNodeTracker

[ https://issues.apache.org/jira/browse/YARN-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387757#comment-15387757 ] Arun Suresh commented on YARN-5414: --- Currently the {{NodeQueueLoadMonitor}} maintains a separate list of

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387775#comment-15387775 ] Arun Suresh commented on YARN-5392: --- [~sunilg], true... also it seems to be used only in testclasses. Did

[jira] [Commented] (YARN-4503) Allow for a pluggable policy to decide if a ResourceRequest is GUARANTEED or not

[ https://issues.apache.org/jira/browse/YARN-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387790#comment-15387790 ] Arun Suresh commented on YARN-4503: --- Moving this out of YARN-4742 umbrella, since it is a general

[jira] [Comment Edited] (YARN-2895) Integrate distributed scheduling with capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387786#comment-15387786 ] Arun Suresh edited comment on YARN-2895 at 7/21/16 2:46 PM: Marking this as

[jira] [Commented] (YARN-5415) Add support for NodeLocal and RackLocal OPPORTUNISTIC requests

[ https://issues.apache.org/jira/browse/YARN-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387831#comment-15387831 ] Arun Suresh commented on YARN-5415: --- YARN-4879 adds support for identifying requests explicitly. This

[jira] [Created] (YARN-5415) Add support for NodeLocal and RackLocal OPPORTUNISTIC requests

Arun Suresh created YARN-5415: - Summary: Add support for NodeLocal and RackLocal OPPORTUNISTIC requests Key: YARN-5415 URL: https://issues.apache.org/jira/browse/YARN-5415 Project: Hadoop YARN

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386594#comment-15386594 ] Arun Suresh commented on YARN-5392: --- Thanks for the taking a look [~leftnoteasy], Agree that currently it

[jira] [Comment Edited] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386676#comment-15386676 ] Arun Suresh edited comment on YARN-5392 at 7/20/16 9:47 PM: [~leftnoteasy], I

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.005.patch Attaching updated patch As per [~leftnoteasy]'s request, I am

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386676#comment-15386676 ] Arun Suresh commented on YARN-5392: --- [~leftnoteasy], I understand we've touched a lot of the code, but

[jira] [Comment Edited] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386676#comment-15386676 ] Arun Suresh edited comment on YARN-5392 at 7/20/16 9:36 PM: [~leftnoteasy], I

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.006.patch Updating patch: Added some javadocs and rolling back some spurious

[jira] [Created] (YARN-5414) Integrate NodeQueueLoadMonitor with ClusterNodeTracker

Arun Suresh created YARN-5414: - Summary: Integrate NodeQueueLoadMonitor with ClusterNodeTracker Key: YARN-5414 URL: https://issues.apache.org/jira/browse/YARN-5414 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Description: Based on discussions in YARN-4888, this jira proposes to replace the use of {{Priority}}

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Description: Based on discussions in YARN-4888, this jira proposes to replace the use of {{Priority}}

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Issue Type: Sub-task (was: Improvement) Parent: YARN-4879 > Replace use of Priority in the

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.002.patch Modified patch to make the {{SchedulerKey}} constructor private and

[jira] [Commented] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381000#comment-15381000 ] Arun Suresh commented on YARN-4888: --- Ping [~leftnoteasy], [~jianhe], [~kasha]... Wondering if we can get

[jira] [Created] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

Arun Suresh created YARN-5392: - Summary: Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey Key: YARN-5392 URL: https://issues.apache.org/jira/browse/YARN-5392 Project:

[jira] [Commented] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381080#comment-15381080 ] Arun Suresh commented on YARN-4888: --- bq. How easy/hard would it be to do this as two patches - one that

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.001.patch Attaching initial patch > Replace use of Priority in the Scheduling

[jira] [Commented] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384596#comment-15384596 ] Arun Suresh commented on YARN-5392: --- ping [~kasha], [~subru].. wondering if you might be able to give

[jira] [Updated] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5350: -- Attachment: YARN-5350.003.patch Thanks for the review [~subru]. Updating testcase with your suggestion..

[jira] [Updated] (YARN-5350) Distributed Scheduling: Ensure sort order of allocatable nodes returned by the RM is not lost

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5350: -- Summary: Distributed Scheduling: Ensure sort order of allocatable nodes returned by the RM is not lost

[jira] [Commented] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385410#comment-15385410 ] Arun Suresh commented on YARN-5350: --- The test failure is unrelated.. checking this in based on [~subru]'s

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.004.patch I see your point [~subru], and agree with you.. As per your suggestion,

[jira] [Resolved] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-4888. --- Resolution: Resolved Temporarily resolving then re-opening to move out of the 'in-progress' status >

[jira] [Reopened] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reopened YARN-4888: --- reopening.. > Changes in RM AppSchedulingInfo for identifying resource-requests explicitly >

[jira] [Updated] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4888: -- Attachment: YARN-4888.001.patch Fixing testcases and findbugs > Changes in RM AppSchedulingInfo for

[jira] [Commented] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380147#comment-15380147 ] Arun Suresh commented on YARN-5181: --- +1, checking this is in shortly.. > ClusterNodeTracker: add method

[jira] [Updated] (YARN-5392) Replace use of Priority in the Scheduling infrastructure with an opaque ShedulerKey

[ https://issues.apache.org/jira/browse/YARN-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5392: -- Attachment: YARN-5392.003.patch Fixing testcases > Replace use of Priority in the Scheduling

[jira] [Commented] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378899#comment-15378899 ] Arun Suresh commented on YARN-5181: --- +1 pending a green jenkins run > ClusterNodeTracker: add method to

[jira] [Updated] (YARN-5338) Fix ContainerId fromString to correctly parse remotely allocated container Ids

[ https://issues.apache.org/jira/browse/YARN-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5338: -- Attachment: YARN-5338.001.patch Attaching trivial patch. > Fix ContainerId fromString to correctly

[jira] [Created] (YARN-5338) Fix ContainerId fromString to correctly parse remotely allocated container Ids

Arun Suresh created YARN-5338: - Summary: Fix ContainerId fromString to correctly parse remotely allocated container Ids Key: YARN-5338 URL: https://issues.apache.org/jira/browse/YARN-5338 Project: Hadoop

[jira] [Created] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

Arun Suresh created YARN-5350: - Summary: Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM Key: YARN-5350 URL: https://issues.apache.org/jira/browse/YARN-5350

[jira] [Updated] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5350: -- Attachment: YARN-5350.001.patch Attaching trivial patch. Most of the code changes are in refactoring the

[jira] [Updated] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5350: -- Fix Version/s: 2.9.0 > Ensure LocalScheduler does not lose the sort order of allocatable nodes >

[jira] [Updated] (YARN-5216) Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM

[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5216: -- Fix Version/s: 2.9.0 > Expose configurable preemption policy for OPPORTUNISTIC containers running on >

[jira] [Updated] (YARN-5350) Ensure LocalScheduler does not lose the sort order of allocatable nodes returned by the RM

[ https://issues.apache.org/jira/browse/YARN-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5350: -- Attachment: YARN-5350.002.patch Updating patch with checkstyle fix. The test failure is spurious... >

[jira] [Commented] (YARN-5216) Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM

[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363748#comment-15363748 ] Arun Suresh commented on YARN-5216: --- Thanks for the patch [~hrsharma] and apologize for the delay. Some

[jira] [Comment Edited] (YARN-5216) Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM

[ https://issues.apache.org/jira/browse/YARN-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363748#comment-15363748 ] Arun Suresh edited comment on YARN-5216 at 7/6/16 4:26 AM: --- Thanks for the patch

[jira] [Commented] (YARN-5351) ResourceRequest should take ExecutionType into account during comparison

[ https://issues.apache.org/jira/browse/YARN-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371190#comment-15371190 ] Arun Suresh commented on YARN-5351: --- Thanks for the patch [~kkaranasos].. I don't think you need to

[jira] [Updated] (YARN-5486) Update OpportunisticConatinerAllocatioAMService allocate method to handle OPPORTUNISTIC container requests

[ https://issues.apache.org/jira/browse/YARN-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5486: -- Assignee: Konstantinos Karanasos (was: Arun Suresh) > Update OpportunisticConatinerAllocatioAMService

[jira] [Created] (YARN-5486) Update OpportunisticConatinerAllocatioAMService allocate method to handle OPPORTUNISTIC container requests

Arun Suresh created YARN-5486: - Summary: Update OpportunisticConatinerAllocatioAMService allocate method to handle OPPORTUNISTIC container requests Key: YARN-5486 URL: https://issues.apache.org/jira/browse/YARN-5486

<    2   3   4   5   6   7   8   9   10   11   >