Hi,
First of all, please properly subscribe to the mailing because otherwise
community will not receive notifications for your messages. Here is the
instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
kvipin wrote
> Hi All,
>
> I'm unable to get apache ignite node in my c++ program which was started
> externally.
>
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
> binary configuration is not equal to remote node's binary configuration
> [locNodeId=6a623d75-8d85-4a05-a38b-4a38ec128b4e,
> rmtNodeId=b56b2b0a-952e-4ffd-9f27-c3c4a58469e9,
> locBinaryCfg={globIdMapper=org.apache.ignite.binary.BinaryBasicIdMapper,
> compactFooter=false, globSerializer=null}, rmtBinaryCfg=null]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1644)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:885)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:334)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1832)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:255)
> ... 9 more
> [14:21:32] Ignite node stopped OK [uptime=00:00:17:593]
To start Java and C++ nodes in the same topology you need to provide
consistent binary configuration. Please refer to this post for the
explanation:
http://apache-ignite-users.70518.x6.nabble.com/Error-starting-c-client-node-using-1-6-tp4697p4719.html
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-apache-ignite-node-started-externally-tp6423p6459.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
