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

ASF GitHub Bot commented on IGNITE-3891:
----------------------------------------

GitHub user shroman opened a pull request:

    https://github.com/apache/ignite/pull/1191

    IGNITE-3891: Enable registering with hostname for zookeeper discovery.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shroman/ignite ignite-3891

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1191.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1191
    
----
commit 2d7667f0ab8c98a12fddc79961442e0421d0ba8d
Author: shtykh_roman <[email protected]>
Date:   2016-10-28T09:41:50Z

    IGNITE-3891: Enable registering with hostname for zookeeper discovery.

----


> Enable writing hostname, rather than ipaddress for zookeeper discovery
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-3891
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3891
>             Project: Ignite
>          Issue Type: Improvement
>          Components: ignite-zookeeper
>    Affects Versions: 1.7
>         Environment: docker
>            Reporter: John Watson
>            Assignee: Roman Shtykh
>
> We are using ignite in docker, with zookeeper discovery. We need to be able 
> to use the hostname, rather than the ip address, since the container-visible 
> ip address is not externally usable.
> We would like an option in the TcpDiscoveryZookeeperIpFinder to use the 
> hostname, rather than ipaddress.  This change would impact line 231, where 
> currently the ip address is being written. We suggest adding an option to the 
> class to use the hostname, rather than the ip address.



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

Reply via email to