hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6041) Opportunistic containers : Combined patch for branch-2
Date Thu, 29 Dec 2016 23:43:58 GMT

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

Wangda Tan commented on YARN-6041:

Removed 2.9.0 from fixVersion, it should be target version.

Just do a very quick scan of the patch, it looks changes are isolated to distributed scheduling
logic inside RM, should be relatively safe. But I hope to get someone more familiar with the
overall opportunistic scheduling logic to make sure it has less impact to existing logics
(especially NM). ([~kasha]?)

Two minor comments for compatibility:
1) ContainerState.java: Mark SCHEDULED to unstable?
2) All new configurations to YarnConfigration.java should be @Unstable. 

And not sure if there's incomplete changes to public (regardless of stablebility) APIs / configs,
we should not merge any API-only changes to branch-2.

> Opportunistic containers : Combined patch for branch-2 
> -------------------------------------------------------
>                 Key: YARN-6041
>                 URL: https://issues.apache.org/jira/browse/YARN-6041
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-6041-branch-2.001.patch
> This is a combined patch targeting branch-2 of the following JIRAs which have already
been committed to trunk :
> YARN-5938. Refactoring OpportunisticContainerAllocator to use SchedulerRequestKey instead
of Priority and other misc fixes
> YARN-5646. Add documentation and update config parameter names for scheduling of OPPORTUNISTIC
> YARN-5982. Simplify opportunistic container parameters and metrics.
> YARN-5918. Handle Opportunistic scheduling allocate request failure when NM is lost.
> YARN-4597. Introduce ContainerScheduler and a SCHEDULED state to NodeManager container
> YARN-5823. Update NMTokens in case of requests with only opportunistic containers.
> YARN-5377. Fix TestQueuingContainerManager.testKillMultipleOpportunisticContainers.
> YARN-2995. Enhance UI to show cluster resource utilization of various container Execution
> YARN-5799. Fix Opportunistic Allocation to set the correct value of Node Http Address.
> YARN-5486. Update OpportunisticContainerAllocatorAMService::allocate method to handle
OPPORTUNISTIC container requests.

This message was sent by Atlassian JIRA

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

View raw message