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

ASF subversion and git services commented on SLIDER-949:
--------------------------------------------------------

Commit 1708722 from [~elserj] in branch 'site/trunk'
[ https://svn.apache.org/r1708722 ]

SLIDER-949 Resource Specification doc fixes (Sherry Guo)

> Fix typos on Slider website 
> ----------------------------
>
>                 Key: SLIDER-949
>                 URL: https://issues.apache.org/jira/browse/SLIDER-949
>             Project: Slider
>          Issue Type: Documentation
>            Reporter: Sherry Guo
>            Assignee: Sherry Guo
>            Priority: Minor
>              Labels: documentation
>         Attachments: SLIDER-949-001.patch
>
>
> Fix typos on the Slider website, in particular, 
> https://slider.incubator.apache.org/docs/configuration/resources.html.
> 1. As it may time for YARN to have the resources to allocate the container, 
> it may take some time for the replacement to be instantiated.
> Should be "At it may take time".
> 2. "components": {
>     "HBASE_MASTER": {
>       "yarn.role.priority": "1",
>       "yarn.component.instances": "1",
>       "yarn.placement.escalate.seconds": "10"
>     },
>     "HBASE_REGIONSERVER": {
>       "yarn.role.priority": "2",
>       "yarn.component.instances": "10",
>       "yarn.placement.escalate.seconds": "600"
>     },
>     "slider-appmaster": {
>     }
> This declares that the HBASE_MASTER placement should be escalated after one 
> second, 
> Should be "after ten seconds".
> 3.
>    Escalation goes directory from "specific node" to "anywhere in cluster"; 
> it does not have any intermediate "same-rack" policy.
> Should be "Escalation goes directly".
> 4. The resources.json file include specifications the labels to be used when 
> allocating containers for the components. 
> Should be "The resources.json file includes specifications of the labels".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to