You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Arun M. Krishnakumar (JIRA)" <ji...@apache.org> on 2016/04/01 19:32:25 UTC

[jira] [Updated] (BOOKKEEPER-910) In LocalBookkeeper, Zookeeper server and client use different host addresses

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun M. Krishnakumar updated BOOKKEEPER-910:
--------------------------------------------
    Attachment: 0001-For-Zookeeper-in-LocalBookkeeper-use-loopback-addres.patch

There is a similar patch needed for the bookies as well, but due to a slightly different problem. I will create another bug for that.

> In LocalBookkeeper, Zookeeper server and client use different host addresses
> ----------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-910
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-910
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.3.2
>            Reporter: Arun M. Krishnakumar
>            Assignee: Arun M. Krishnakumar
>            Priority: Minor
>              Labels: easyfix
>         Attachments: 0001-For-Zookeeper-in-LocalBookkeeper-use-loopback-addres.patch
>
>
> In LocalBookkeeper, the Zookeeper server is started at 127.0.0.1 and the client tries to derive the localhost address using getLocalHost API. This has a few issues:
> 1. There is a possibility of using the ipv6 address for localhost and hence the client will try connecting to ::1, 2181 rather than 127.0.0.1:2181 (this happens commonly on OSX)
> 2. The getLocalHost API could sometimes return non-loopback addresses as well
> Since the 'localbookie' mode is used with the zookeeper in the same machine, we should use loopback addresses for all invocations.
>  



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