Ignite TcpDiscoveryS3IpFinder and AWS VPC

classic Classic list List threaded Threaded
2 messages Options
smovva smovva
Reply | Threaded
Open this post in threaded view
|

Ignite TcpDiscoveryS3IpFinder and AWS VPC

I have a cluster running on AWS VPC with TcpDiscoveryS3IpFinder SPI. I
noticed that there are a couple of  entries in the S3 bucket
'127.0.0.1#47500', '0:0:0:0:0:0:0:1%lo#47500' along with entries for the
private IPs of the nodes. If anyone understands what these are, can you
please share the info.

Also, I have another VPC that I want to run some clients from. I was
wondering if there is any documentation around setting up VPC peering and
address translation for this to work.

Thanks



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
aealexsandrov aealexsandrov
Reply | Threaded
Open this post in threaded view
|

Re: Ignite TcpDiscoveryS3IpFinder and AWS VPC

Hi,

According '127.0.0.1#47500', '0:0:0:0:0:0:0:1/0#47500':

It's just the different views of the same address (localhost). For example,
Ignite started on 10.0.75.1 could be available using next addresses from the
same node:

>>> Local node addresses: [LAPTOP-I5CE4BEI/0:0:0:0:0:0:0:1,
>>> LAPTOP-I5CE4BEI.mshome.net/10.0.75.1, LAPTOP-I5CE4BEI/127.0.0.1,
>>> LAPTOP-I5CE4BEI.gridgain.local/172.18.24.193, /172.25.4.187,
>>> /192.168.56.1]

0:0:0:0:0:0:0:1/0 is a CIDR notation. You can read more about it here:

https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation

According to VPC Peering and Ignite. I don't think that this scenario was
tested. However, you can try to follow common suggestion about how it should
be:

https://docs.aws.amazon.com/vpc/latest/peering/peering-scenarios.html

BR,
Andrei





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/