In the interest of full disclosure, I have fixed the failing test as shown in http://is.gd/HsrHGf but I am fairly sure it might/will pop-up in the actual deployment, because the client node will be started with OptimizedMarshaller anyway.
Cos On Mon, Jan 04, 2016 at 08:40PM, Konstantin Boudnik wrote: > Fellas, > > I have noticed a weird thing while working on upgrading Ignite in Zeppelin. > One of the tests failed because of > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's > marshaller differs from remote node's marshaller (to make sure all nodes in > topology have identical marshaller, configure marshaller explicitly in > configuration) > [locMarshaller=org.apache.ignite.marshaller.optimized.OptimizedMarshaller, > rmtMarshaller=org.apache.ignite.internal.binary.BinaryMarshaller, > > locNodeAddrs=[testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1, > /127.0.0.1, /172.17.12.239], locPort=0, > > rmtNodeAddr=[testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1, > /127.0.0.1, /172.17.12.239], locNodeId=8fa598a2-9986-4f29-ba8d-8f857048e227, > rmtNodeId=3aa33408-afea-48c7-941c-8ea87429f44d] > > At the glance, it seems like running nodes in server and client modes somehow > trigger different defaults for the marshallers, but I wasn't able to quickly > find anything in the code proving my point. > > I've ended up forcing OptimizedMarshaller for the server node in the Zep's > > ignite/src/test/java/org/apache/zeppelin/ignite/IgniteSqlInterpreterTest.java > and it solved the immediate issue. However, the situation seems worthy noting > on dev@ > > Cheers, > Cos >
signature.asc
Description: Digital signature
