Thanks Igor.

Yes it is trying to start in client mode now with correct file. My bad
filename misspelled by a character.

Now im getting following error:
[09:55:28] REST protocols do not start on client node. To start the
protocols on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system
property.
[09:55:29,110][SEVERE][main][IgniteKernal] Failed to start manager:
GridManagerAdapter [enabled=true,
name=o.a.i.i.managers.discovery.GridDiscoveryManager]
class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller
[clsFilter=org.apache.ignite.marshaller.MarshallerUtils$1@6c0d9d86],
reconCnt=10, reconDelay=2000, maxAckTimeout=600000, forceSrvMode=false,
clientReconnectDisabled=false, internalLsnr=null]
        at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
        at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:915)
        at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1721)
        at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1028)
        at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
        at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
        at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
        at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:649)
        at
org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
        at
org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:75)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
binary configuration is not equal to remote node's binary configuration
[locNodeId=3a0f06e7-b430-4e70-83cd-69d5067fb06f,
rmtNodeId=de5d439d-bbfa-4446-aeaf-4beedb6c4953,
locBinaryCfg={globIdMapper=org.apache.ignite.binary.BinaryBasicIdMapper,
compactFooter=false, globSerializer=null}, rmtBinaryCfg=null]
        at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1874)
        at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1771)
        at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


IS IT LIKE WE SHOULD HAVE EXACT SAME XML FILES with DISCOVERYSPI
configuration having IPs of all the server and client nodes in it?
Mine is:

        <property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    
                   <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                    <property name="addresses">
                        <list>
                            <value>10.42.27.121:47500..47509</value>  --->
this is server
                            <value>10.42.27.131:47500..47509</value>  --->
this is another server
                            <value>10.42.27.125:47500..47509</value>   ---->
this is c++ client im starting
                        </list>
                    </property>
                  </bean>
                </property>
            </bean>
        </property>


If this is the case what if i need to scale with another client in new IP to
the cluster?
Please clarify.

Thanks,
...summa




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to