We were able to reproduce the issue (thanks to the test code you've sent) and have found the reason (remaining index data on old node during migration, in some cases) behind it. We are working on a fix that will be available in version 2.4.1.
@mmdogan
~Sent from mobile
--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To post to this group, send email to haze...@googlegroups.com.
To unsubscribe from this group, send email to hazelcast+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hazelcast?hl=en.
Fixed. Will be released today or in a few days