Hi all
I'm installing a persistence apache-ignite in Kubernetes using the Chart
available in the official web. After some troubleshooting 2 nodes of ignite
are running and some SQL DBs were created with their caches.
The method used to discover nodes is based in auto-discovery of Kubernetes.
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
<property name="peerClassLoadingEnabled" value="false"/>
<!-- Explicitly configure TCP discovery SPI to provide list of
initial nodes. -->
<property name="discoverySpi">
<bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder">
<property name="namespace" value="default"/>
<property name="serviceName"
value="my-ignite-service"/>
</bean>
</property>
</bean>
</property>
</bean>
The problem I see is when I try to load the Visor and open the
configuration. If I use the same config file that is used by ignite.sh the
Visor can not connect to the Grid (topology is empty). I have to create a
different configuration file specifying the IP (fortunately my kubernetes
has only a node: 127.0.0.1). Next configuration is ok for a Kuebernes with
only a node and visor connects to the grid.
<property name="discoverySpi">
<bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
<property name="addresses">
<list>
<!-- In distributed environment, replace
with actual host IP address. -->
<value>127.0.0.1:47500..47509</value>
</list>
</property>
</bean>
</property>
</bean>
</property>
More info: I see the Kubernets libraries are loaded in both process
(inginte.sh and visor) but visor doesnt apply the kubernetes configuration.
No error appears. The Kurbernetes auto-discovery is desirable to install
Ignite in Kubernetes production environments.
Did you experience this issue? any workaround?
