Failed to process message: Creating partition which does not belong to local node

[yucigou <yu...@gmail.com>]

Hi,

Our app is getting the following error messages. Wonder what is all about.
Should I go check the key.hashCode() implementations, but the log does not
point out which key it's talking about. What would the indication of this
message be: something seriously wrong with the cluster?

Many thanks,
Yuci

[12:55:32,875][ERROR][sys-#30%null%][GridCacheIoManager] Failed to process
message [senderId=c08bb6cc-c737-4122-bfcc-3b96f9f19b64, messageType=class
o.a.i.i.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest]
class
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException
[part=13, msg=Creating partition which does not belong to local node (often
may be caused by inconsistent 'key.hashCode()' implementation) [part=13,
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0
], this.topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0]]]
        at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:713)
        at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:656)
        at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:68)
        at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:84)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.entry0(GridCacheAdapter.java:971)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:939)
        at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:404)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:930)
        at
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:143)
        at
org.apache.ignite.internal.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:987)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:775)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:353)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:277)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:88)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:231)
        at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1238)
        at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:866)
        at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
        at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:829)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-process-message-Creating-partition-which-does-not-belong-to-local-node-tp9332.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Failed to process message: Creating partition which does not belong to local node

[vkulichenko <va...@gmail.com>]

Hi Yuci,

Basically, this error means that affinity function on node A gave node B as
a primary node for a key. Node A than sent a request to node B, but affinity
on node B doesn't think that this key belong locally. In other words,
affinity function worked inconsistently on different nodes.

Usually this is caused by incorrect hashCode() implementation of the key
class (as pointed out in the message). Unfortunately, the key itself is not
printed out, so I would recommend to put a breakpoint and go back through
the trace to see for which key the partition number is calculated
incorrectly.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-process-message-Creating-partition-which-does-not-belong-to-local-node-tp9332p9341.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.