[
https://issues.apache.org/jira/browse/YARN-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848052#comment-13848052
]
Vinod Kumar Vavilapalli commented on YARN-1028:
-----------------------------------------------
bq. My initial patch had it that way, [...]
Trying to keep all of fail-over stuff in one place. What else would need to
move? In any case, we can delay this change till we fix all the other things in
this patch.
bq. Thinking more about it, we could compute numFailovers using
connect.max-wait-ms when yarn.client.failover.max-attempts is not specified
Yeah, something like that. It's few too many configs now for admins to
understand and set.
> Add FailoverProxyProvider like capability to RMProxy
> ----------------------------------------------------
>
> Key: YARN-1028
> URL: https://issues.apache.org/jira/browse/YARN-1028
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Karthik Kambatla
> Attachments: yarn-1028-1.patch, yarn-1028-2.patch, yarn-1028-3.patch,
> yarn-1028-4.patch, yarn-1028-5.patch, yarn-1028-6.patch, yarn-1028-7.patch,
> yarn-1028-8.patch, yarn-1028-draft-cumulative.patch
>
>
> RMProxy layer currently abstracts RM discovery and implements it by looking
> up service information from configuration. Motivated by HDFS and using
> existing classes from Common, we can add failover proxy providers that may
> provide RM discovery in extensible ways.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
