ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olexandr K <olexandr.kundire...@gmail.com>
Subject Strange cluster activation behaviour in ignite 2.4.0
Date Thu, 26 Apr 2018 09:14:09 GMT
Hi Igniters,

I observe strange cluster activation behaviour in ignite 2.4.0

1) start 2 server nodes
2) control.bat --state => Cluster is inactive
3) control.bat --activate => Cluster activated
4) stop both nodes
5) start them again
6) control.bat --state => Cluster is active

Q: why my cluster was auto-activated on restart? Is it expected?

I didn't run any "control.bat --baseline" command

OS : Windows Server 2012 R2

<property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="localPort" value="47500"/>
                <property name="localPortRange" value="4"/>
                <property name="ipFinder">
                    <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">

                        <property name="addresses">
                            <list>
                                <value>host1:47500..47504</value>
                                <value>host2:47500..47504</value>
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>

Mime
View raw message