[
https://issues.apache.org/jira/browse/IGNITE-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622632#comment-15622632
]
Andrey Gura commented on IGNITE-3891:
-------------------------------------
Guys, I don't sure that understand correctly this issue, but it seems that
{{AddressResolver}} should help in case of Ignite nodes in docker container are
registered with internal addresses. If problem is in Zookeeper connection then
you can provide connection string or Courator instance to
{{TcpDiscoveryZookeeperIpFinder}}. It should be enough and doesn't require any
code changes. See javadoc.
> 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)
