ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Zookeeper Discovery SPI & external IP address in AWS
Date Thu, 22 Jun 2017 01:08:43 GMT
Anton, Nikolay,

Looks like you participated in the fix. Can you please check?

-Val

On Wed, Jun 21, 2017 at 7:01 PM Igor Rudyak <irudyak@gmail.com> wrote:

> Thanks Val,
>
> It looks like there is still this problem in version 2.0.0
>
> Igor
>
> On Wed, Jun 21, 2017 at 3:20 PM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
> > 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
> > > > >
> > > >
> > >
> >
>

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