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
The following test works with hazelcast 2.6.9 but fails with hazelcast 3.2.3 on the first assertEquals. The counter "lockedEntryCount" is always 0.
Moreover, the method getLockWaitCount has been removed but nothing indicates if this data is still accessible somewhere. We use in our project this two counters to monitor cluster-wide locks.
Current behavior: First you should put an entry with the key "lock" then you can expect this will appear in the stats. AFAIS you are not putting an entry in your test.
Ok so the behavior has changed between 2.6.9 and 3.2.3.
And what about the removed method (getLockWaitCount), is there a way to get number of threads waiting for the locks ? Or is it no longer available ?
Thanks
getLockWaitCount is not available in 3.x and no simple workaround seems can be done atm, If you want you can create a separate feature request issue for it.
The following test works with hazelcast 2.6.9 but fails with hazelcast 3.2.3 on the first assertEquals. The counter "lockedEntryCount" is always 0.
Moreover, the method getLockWaitCount has been removed but nothing indicates if this data is still accessible somewhere. We use in our project this two counters to monitor cluster-wide locks.
The text was updated successfully, but these errors were encountered: