ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Rudyak <irud...@gmail.com>
Subject Zookeeper Discovery SPI & external IP address in AWS
Date Wed, 21 Jun 2017 06:30:11 GMT
Hi guys,

How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP address
(in addition to private IP) of Ignite node when it's deployed in Amazon?

By default it just publishing private IP addresses of nodes which makes it
impossible to connect to cluster from outside using *Zookeeper Discovery
SPI*.

I tried to use something like this (see below) for *discoverySPI*:

<property name="discoverySpi">
<bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="addressResolver">
<bean class="org.apache.ignite.configuration.BasicAddressResolver">
<constructor-arg>
<map>
<entry key="<node-private-ip>" value="<node-public-ip>"/>
</map>
</constructor-arg>
</bean>
</property>
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.TcpDiscoveryZookeeperIpFinder">
<property name="zkConnectionString" value="<zookeeper-ip>:2181"/>
</bean>
</property>
</bean>
</property>

But such way it only publish public IPs to Zookeeper.

Actually I am looking for something like *advertised.host.name
<http://advertised.host.name>* analog in Kafka. Which allows to publish
private and public IP addresses for a node to Zookeeper.

Such way all internal services communicates through private IPs, but
external services communicates using public IPs.

Igor

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message