We have recently upgraded our Hazelcast platform version from 3.12.13 to 5.2.2. After the upgrade we are facing: com.hazelcast.core.OperationTimeoutException GetOperation invocation failed to complete due to operation-heartbeat-timeout.
We use a two node Hazelcast cluster. In our Java application code we use several IMaps. The exception is always happening while performing a get operation on one particular IMap. This happens around the same time a node is also performing remove operations on this IMap. It is possible that the key for both the remove and get operations are the same. The application ran fine with 3.12.13. Is there any difference between the versions that may cause this operation timeout?
This message contains information that may be privileged or confidential and is the property of Striim, Inc. and its subsidiaries. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message and any attachments. --
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/299e5da8-51b2-4112-89e4-ea9781f4bb05n%40googlegroups.com.