I tried to configure two Ignite.NET Standalone Nodes on two different servers (as server nodes) with authentication. For the authentication it requires persistent storage be enabled for at least one data region and to activate a cluster. I configured the first node and activate the cluster. When I moved to second node and configure it exactly as the first node it somehow added it to the first luster with no discovery configuration. in the first node I changed the password of the ignite user and when I tried to connect to the second node with the default password it rejected me and accept only the first node password. my question is how the second node know this password and joined to the cluster automatically?
IP addresses of the nodes x.y.z.220 x.y.z.221
Apache.ignite.exe.config:
<igniteConfiguration xmlns="http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection">
<cacheConfiguration>
<cacheConfiguration>
<name>default</name>
</cacheConfiguration>
</cacheConfiguration>
<clientConnectorConfiguration type="ClientConnectorConfiguration">
<port>6379</port>
</clientConnectorConfiguration>
<dataStorageConfiguration>
<defaultDataRegionConfiguration>
<name>Default_Region</name>
<persistenceEnabled>true</persistenceEnabled>
</defaultDataRegionConfiguration>
</dataStorageConfiguration>
<authenticationEnabled>true</authenticationEnabled>
</igniteConfiguration>
Ignite uses Multicast discovery by default, and nodes within the same subnet find each other automatically.
To avoid this, configure an IP finder. You can use loopback address to make sure the node won't connect to other nodes outside of the current machine:
<discoverySpi type="TcpDiscoverySpi">
<ipFinder type="TcpDiscoveryStaticIpFinder">
<endpoints>
<string>127.0.0.1:47500</string>
</endpoints>
</ipFinder>
</discoverySpi>