[
https://issues.apache.org/jira/browse/YARN-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745975#comment-15745975
]
Konstantinos Karanasos commented on YARN-5646:
----------------------------------------------
Thanks for the feedback, [~kasha]!
Regarding some of your comments:
bq. We should honor some character limit for the lines.
The problem is that markdown adds a new line in HTML for each new line in the
text, so the HTML ends up not looking good. That's why there are no line wraps
in any of the YARN md files I checked.
bq. Can we discuss execution before allocation?
I had it like that in an initial version :), and then changed it back to follow
the actual order of actions (allocation before execution). But I will check it
again and might switch it back if it looks better (or add a forward pointer if
I keep the current order).
bq. Can we automatically turn on AMRMProxy if someone enables
distributed-opportunistic-scheduling?
Makes sense, will do.
bq. The configs don't seem to follow general YARN conventions.
You are right. I think we had it like that at some point, but things changed
across iterations. Will make sure we follow the conventions.
I got the diff, will check it as well. I will work on the document today or
tomorrow and will upload a new version addressing the comments of all of you.
> Documentation for scheduling of OPPORTUNISTIC containers
> --------------------------------------------------------
>
> Key: YARN-5646
> URL: https://issues.apache.org/jira/browse/YARN-5646
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Priority: Blocker
> Attachments: YARN-5646.001.patch
>
>
> This is for adding documentation regarding the scheduling of OPPORTUNISTIC
> containers.
> It includes both the centralized (YARN-5220) and the distributed (YARN-2877)
> scheduling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
