You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In hazelcast 3.0.3, there's a bug during MapLoading. If the master (oldest) node doesn't own any keys from the Set loadAllKeys() gave back, the map will be stuck in not ready state forever.
If it is accessed, after a while it will start throwing "RetryableHazelcastException: Map is not ready" exceptions.
This is not a problem when loadAllKeys() give back 0 or many keys, but can happen easily, if it gives back only a few.
The easiest way to recreate is to start many instances, and have loadAllKeys() give back only 1 key.
The text was updated successfully, but these errors were encountered:
In hazelcast 3.0.3, there's a bug during MapLoading. If the master (oldest) node doesn't own any keys from the Set loadAllKeys() gave back, the map will be stuck in not ready state forever.
If it is accessed, after a while it will start throwing "RetryableHazelcastException: Map is not ready" exceptions.
This is not a problem when loadAllKeys() give back 0 or many keys, but can happen easily, if it gives back only a few.
The easiest way to recreate is to start many instances, and have loadAllKeys() give back only 1 key.
The text was updated successfully, but these errors were encountered: