Re: Ignite YARN deployment - how to use TCP IP Discovery?

[Ilya Kasnacheev <il...@gmail.com>]

Hello!

I think that you actually have some problems with network connectivity. "
sparkmaster002.wbd.zjztc.cn/192.168.48.41:47500" is an internal Ignite
representation of IP address, what actually gets used for connect is middle
part.

Regards,
-- 
Ilya Kasnacheev


сб, 11 июл. 2020 г. в 13:24, 38797715 <38...@qq.com>:

> Hi ,
>
> In YARN environment, if TcpDiscoveryVmIpFinder is used for discovery, the
> following address is specified:
> sparkmaster001.wbd.zjztc.cn
> sparkmaster002.wbd.zjztc.cn
>
> However, the discovery failed, indicating the following error, we find
> that the resolved address becomes the following form:
> sparkmaster002.wbd.zjztc.cn/192.168.48.41:47500
>
> How to solve this problem?
> The same address can be found in the local environment.
> 在 2019/11/6 下午9:17, Andrei Aleksandrov 写道:
>
> Hi,
>
> I guess you can try collect all IP addresses from all nodes that managed
> by YARN (where you are going to start Ignite) and add them all to addresses
> into TcpDiscoveryVmIpFinder part of Ignite configuration.
>
> Also you should provide the guarantee that each such hosts will be able to
> connect each other.
>
> BR,
> Andrei
> 11/5/2019 9:15 PM, Seshan, Manoj N. (TR Tech, Content & Ops) пишет:
>
> We are using Ignite as a Distributed In-Memory cache, deployed using YARN
> on a Hadoop Cluster.  We have configured Zookeeper Discovery, and this is
> working fine.
>
>
>
> Given this is a small 20 node Ignite cluster, Zookeeper Discovery seems
> overkill. Would it be possible to switch to TCP Discovery? Multicast
> Finding is not an option, as that is disabled. Static IP Finding would also
> not work, as the Ignite Containers are dynamically allocated by YARN to
> arbitrary nodes of the Hadoop Cluster.
>
>
>
> Rgds
>
>
>
> *Manoj Seshan - Senior Architect*
>
> Platform Content Technology, Bangalore
>
> [image: cid:image001.gif@01C95541.6801BF70]
>
> *Voice:* +91-98806 72987  +91-80-67492572
>
>
>
>