[jira] [Comment Edited] (YARN-6619) AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest objects

2018-01-14 Thread Arun Suresh (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325891#comment-16325891
 ] 

Arun Suresh edited comment on YARN-6619 at 1/15/18 5:00 AM:


Attaching initial patch.
 * Modified the {{TestAMRMClient}} testcase to refactor out some common code to 
a separate class.
 * The test uses the asyncAMRMClient, since that way both the async client and 
the normal client will be tested, since the async client uses the normal client 
internally.
* The general flow is, if the {{PlacementProcessor}} is enabled, the client has 
to call {{addPlacecmentConstraint}} before registering with the RM. The client 
can then use {{addSchedulingRequests(Collection)}} to add a 
collection of scheduling requests. All scheduling requests in the collection 
are guaranteed to be sent in the same allocate call.
* The patch also has some minor bug fixes to ensure end 2 end, things work fine.


was (Author: asuresh):
Attaching initial patch.
 * Modified the {{TestAMRMClient}} testcase to refactor out some common code to 
a separate class.
 * The test uses the asyncAMRMClient, since that way both the async client and 
the normal client will be tested, since the async client uses the normal client 
internally.
* The general flow is, if the {{PlacementProcessor}} is enabled, the client has 
to call {{addPlacecmentConstraint}} before registering with the RM. The client 
can then use {{addSchedulingRequests}} to add a collection of scheduling 
requests. All scheduling requests the one call to the above method are 
guaranteed to be sent in the same allocate call.
* The patch also has some minor bug fixes to ensure end 2 end, things work fine.

> AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest 
> objects
> 
>
> Key: YARN-6619
> URL: https://issues.apache.org/jira/browse/YARN-6619
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Arun Suresh
>Assignee: Arun Suresh
>Priority: Major
> Attachments: YARN-6619-YARN-6592.001.patch
>
>
> Opening this JIRA to track changes needed in the AMRMClient to incorporate 
> the PlacementConstraint and SchedulingRequest objects



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Comment Edited] (YARN-6619) AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest objects

2018-01-05 Thread Panagiotis Garefalakis (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313879#comment-16313879
 ] 

Panagiotis Garefalakis edited comment on YARN-6619 at 1/5/18 9:06 PM:
--

[~asuresh] not at all, it depends on YARN-7696 so it makes sense.


was (Author: pgaref):
[~asuresh] not at all, it relates with YARN-7696 so it makes sense.

> AMRMClient Changes to use the PlacementConstraint and SchcedulingRequest 
> objects
> 
>
> Key: YARN-6619
> URL: https://issues.apache.org/jira/browse/YARN-6619
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Arun Suresh
>Assignee: Arun Suresh
>
> Opening this JIRA to track changes needed in the AMRMClient to incorporate 
> the PlacementConstraint and SchedulingRequest objects



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org