You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by vkulichenko <va...@gmail.com> on 2017/07/06 21:40:16 UTC

Re: Volatile Kubernetes Node Discovery

Hi Stephen,

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscribe@ignite.apache.org and follow simple instructions in
the reply.


macdonagh wrote
> Are there logs which will show the Kubernetes IP finder doing its job ?
> 
> I am running a similar scenario but i do not get as far.
> I expected to see traces from TcpDiscoveryKubernetesIpFinder in the ignite
> log but i do not.
> 
> Instead i see a warning 
> 
> [16:47:22,838][WARNING][main][TcpDiscoveryMulticastIpFinder]
> TcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is
> recommended in production to specify at least one address in
> TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
> 
> even though my configuration file only contains the KubernetesIPFinder
> bean class.

You most likely misconfigured something. There is no way you will see logs
from TcpDiscoveryMulticastIpFinder if TcpDiscoveryKubernetesIpFinder is
configured. Check that correct configuration file is used.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Volatile-Kubernetes-Node-Discovery-tp12357p14418.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.