[
https://issues.apache.org/jira/browse/YARN-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270416#comment-16270416
]
Konstantinos Karanasos commented on YARN-5542:
----------------------------------------------
bq. If there is such document available, please share in the jira so I can
check how many things need to be done before getting this to production.
[~cheersyang], we did not finalize that document, so it is currently not
available for sharing. Essentially it described the whole effort of using both
opportunistic containers and overcommitment of resources (YARN-1011).
However, the documentation on opportunistic containers that is available in the
Hadoop release (YARN-5464) should be enough to get you started, especially
given that YARN-1011 is not finalized yet.
I would suggest to start experimenting with the current version in 2.9 and see
how it works for you, so that we can then discuss your use cases. Also, from
what you mentioned in YARN-2889, if you need some apps to be given only
opportunistic containers, you will need to do some changes in the AM.
Feel free to post more questions or any other findings here, so that we can
help along the way.
PS: I reverted the JIRA to its old title, as I remembered that it was created
to group all JIRAs related to the scheduling of opportunistic containers.
> Scheduling of opportunistic containers
> --------------------------------------
>
> Key: YARN-5542
> URL: https://issues.apache.org/jira/browse/YARN-5542
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Konstantinos Karanasos
>
> This JIRA groups all efforts related to the scheduling of opportunistic
> containers.
> It includes the scheduling of opportunistic container through the central RM
> (YARN-5220), through distributed scheduling (YARN-2877), as well as the
> scheduling of containers based on actual node utilization (YARN-1011) and the
> container promotion/demotion (YARN-5085).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
