Hello!
For thick clients, you need both 47100 and 47500, both directions (perhaps
for 47500 only client -> server is sufficient, but for 47100, both are
needed).
For thin clients, 10800 is enough. For control.sh, 11211.
Regards,
--
Ilya Kasnacheev
пт, 26 июн. 2020 г. в 22:06, John Smith <java.dev....@gmail.com>:
> I'm askin in separate question so people can search for it if they ever
> come across this...
>
> My server nodes are started as and I also connect the client as such.
>
> <bean
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> <property name="addresses">
> <list>
> <value>foo:47500</value>
> ...
> </list>
> </property>
> </bean>
>
> In my client code I used the basic address resolver
>
> And I put in the map
>
> "{internalHostIP}:47500", "{externalHostIp}:{externalPort}"
>
> igniteConfig.setAddressResolver(addrResolver);
>
>
> QUESTIONS
> ___________________
>
> 1- Port 47500 is used for discovery only?
> 2- Port 47100 is used for actual coms to the nodes?
> 3- In my container environment I have only mapped 47100, do I also need to
> map for 47500 for the Tcp Discovery SPI?
> 4- When I connect with Visor and I try to look at details for the client
> node it blocks. I'm assuming that's because visor cannot connect back to
> the client at 47100?
> Se logs below
>
> LOGS
> ___________________
>
> When I look at the client logs I get...
>
> IgniteConfiguration [
> igniteInstanceName=xxxxxx,
> ...
> discoSpi=TcpDiscoverySpi [
> addrRslvr=null, <--- Do I need to use BasicResolver or here???
> ...
> commSpi=TcpCommunicationSpi [
> ...
> locAddr=null,
> locHost=null,
> locPort=47100,
> addrRslvr=null, <--- Do I need to use BasicResolver or here???
> ...
> ],
> ...
> addrRslvr=BasicAddressResolver [
> inetAddrMap={},
> inetSockAddrMap={/internalIp:47100=/externalIp:2389} <----
> ],
> ...
> clientMode=true,
> ...
>
>
>
