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

Subru Krishnan commented on YARN-6807:
--------------------------------------

Thanks [~tanujnay] for trying out Federation and reporting the issues you 
faced! 

I looked at your documentation patch, please find my comments below:
* Please run mvn site locally to check the syntax.
* The configuration of {{FederationClientInterceptor}} in the router 
interceptor pipeline is missing.
* Nit: move the _amrmproxy.enabled_ flag to be the first config in NM for 
consistency.
* Call out why we always require *FederationRMFailoverProxyProvider* to be 
configured.
* Rename *Operation --> Running a sample job in a Federated cluster*
* The value of _yarn.resourcemanger.scheduler.address_ should be 
_localhost:8049_ as that's the {{AMRMProxy}} address.
* Please clarify why we need the additional configs in client _yarn-site.xml_.
* Link to the main getting started guide for how to bring up the individual 
clusters.
* Nit: missing formatting of the router start command.
* It'll be good if you add the steps & output of running a sample job, say *Pi*.

> Adding required missing configs to Federation configuration guide based on 
> e2e testing
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-6807
>                 URL: https://issues.apache.org/jira/browse/YARN-6807
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: documentation, federation
>    Affects Versions: YARN-2915
>            Reporter: Subru Krishnan
>            Assignee: Tanuj Nayak
>         Attachments: YARN-6807-YARN-2915-v1.patch
>
>
> We identified some missing configs that are required for e2e run. This JIRA 
> proposes to update the documentation to include the same.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to