Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMpMOYGNeSAv3va1xP1mRvc7iFRBH=czRDuO7-ke9arhQtuWEA@mail.gmail.com>
References: <CAMpMOYFFZ+erzhhfpOcS42_6=LNBBT+vuyJVV8bM=jfFCZiSbg@mail.gmail.com>
 <CABuYRcpUKis1H2bVF8LdqYfZOKM9QbrrR9jw0riQNz4CY_Y7wQ@mail.gmail.com> <CAMpMOYGNeSAv3va1xP1mRvc7iFRBH=czRDuO7-ke9arhQtuWEA@mail.gmail.com>
From: Valentin Kulichenko <valentin.kulichenko@gmail.com>
Date: Wed, 21 Jun 2017 15:20:31 -0700
Message-ID: <CABuYRcqdkHUq-v9-ZCDwHp=qqM5PMANeiM_QbiakZPqRG08PBA@mail.gmail.com>
Subject: Re: Zookeeper Discovery SPI & external IP address in AWS
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c07701a80c0f305527fc863"
archived-at: Wed, 21 Jun 2017 22:21:13 -0000

--94eb2c07701a80c0f305527fc863
Content-Type: text/plain; charset="UTF-8"

Igor,

Here is the ticket I'm talking about:
https://issues.apache.org/jira/browse/IGNITE-3230

-Val

On Wed, Jun 21, 2017 at 8:57 AM, Igor Rudyak <irudyak@gmail.com> wrote:

> Val,
>
> Are there any ticket for this in Jira?
>
> Igor
>
> On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
> valentin.kulichenko@gmail.com> wrote:
>
> > Igor,
> >
> > What version are you going on? I believe we already fixed this in the
> past.
> >
> > -Val
> >
> > On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak <irudyak@gmail.com> wrote:
> >
> > > 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
> > >
> >
>

--94eb2c07701a80c0f305527fc863--