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

Bikas Saha commented on YARN-1660:
----------------------------------

Its great that we are making these ease of use changes. But unfortunately, 
there are no comments/javadoc/example configuration in the defaults files that 
is showing people how they can go about easily configuring their RM's in 
different ways. I can try to read the code carefully and experiment with 
configs to figure things out, but right now its not clear to me what is the 
minimal config I can use to get started. On the other side of the spectrum, can 
I specify the exact hostname and port for every service? Do I have to suffix it 
with RM id? Can I specify some specific ports and leave the remaining 
hostname/ports to be filled in by the RM? Do I need to suffix those with RM id?
I am sure this is common knowledge among the folks working on this but that may 
not hold for everyone. Or it may just be that I am slow in understanding stuff 
this morning :P


> add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting 
> all the various host:port properties for RM
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1660
>                 URL: https://issues.apache.org/jira/browse/YARN-1660
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Arpit Gupta
>            Assignee: Xuan Gong
>             Fix For: 2.4.0
>
>         Attachments: YARN-1660.1.patch, YARN-1660.2.patch
>
>
> Currently the user has to specify all the various host:port properties for 
> RM. We should follow the pattern that we do for non HA setup where we can 
> specify yarn.resourcemanager.hostname.rm-id and the defaults are used for all 
> other affected properties.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to