[
https://issues.apache.org/jira/browse/KUDU-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425883#comment-17425883
]
ASF subversion and git services commented on KUDU-75:
-----------------------------------------------------
Commit 3884a6388b2696a826b8903144ae555faa595473 in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=3884a63 ]
[consensus] KUDU-1620: re-resolve consensus peers on network error
This plumbs the work from KUDU-75 into the long-lived consensus proxy,
allowing Raft peers to re-resolve on error.
This has the knock-on effect that masters starting up also re-resolve
other masters' address when attempting to fetch UUIDs, since this
process also uses consensus proxies.
Change-Id: Ibd1b68c3c14d7d8f81168e16fe450d2ffcce840b
Reviewed-on: http://gerrit.cloudera.org:8080/17868
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <[email protected]>
> Allow RPC proxies to take HostPort and do DNS resolution inline with calls
> --------------------------------------------------------------------------
>
> Key: KUDU-75
> URL: https://issues.apache.org/jira/browse/KUDU-75
> Project: Kudu
> Issue Type: Improvement
> Components: rpc
> Affects Versions: M4
> Reporter: Todd Lipcon
> Priority: Major
>
> A lot of RPC calls will be done against host/ports rather than ip/ports. We
> should make the Proxy itself do the resolution inline in the async path (and
> perhaps have some method to refresh DNS)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
