Re: TcpDiscoverySpi worker thread failed with assertion error

Thanks, Mike! I will update and verify it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

TcpDiscoverySpi worker thread failed with assertion error

Sorry for using the same topic of http://apache-ignite-users.70518.x6.nabble.com/TcpDiscoverySpi-worker-thread-failed-with-assertion-error-td14554.html Actually I met the same issue exactly, although it was fixed in https://issues.apache.org/jira/browse/IGNITE-5562 We have more than 6 clusters,

Re: The CPU of Ignite NODEs in the same cluster has 20% gap

6 CPU processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz stepping: 2 microcode : 1808 cpu MHz : 2700.000 cache size : 20480 KB physical id : 10 siblings: 1

Re: The CPU of Ignite NODEs in the same cluster has 20% gap

6 CPU processor : 5 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz stepping: 2 microcode : 1808 cpu MHz : 2700.000 cache size : 20480 KB physical id : 10 siblings: 1

Re: The CPU of Ignite NODEs in the same cluster has 20% gap

Update the jvisualvm screenshot. --

The CPU of Ignite NODEs in the same cluster has 20% gap

We have a cluster has 20 nodes. 18 nodes work as http servers, 2 nodes work as cache servers. The 18 nodes query data from the 2 cache servers via IgniteService and IgniteCache. But on the load testing, the CPU of 2 cache severs has 20% gap.

Re: Cannot exchange messages between two nodes.

Thanks all. I resolve it, since the second node didn't remoteListen by an inner logic. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Cannot exchange messages between two nodes.

The two nodes have the same subscriber. The only difference is the order of starting node. The first started node, we call it as Node1, the second started node is Node2. The Node1 send a message, the Node2 will handle it as expected in remoteListen(@Nullable Object topic, IgniteBiPredicate p) But

Cannot exchange messages between two nodes.

Hello experts, I met an issue on topic based messaging between two Ignite nodes. I start two nodes one by one. The first started node send a message, the second node can receive the message and handle it in the predicate as expected.