Mael Le Guével <[email protected]>: Author Summary

Builds triggered by Mael Le Guével <[email protected]>

Builds triggered by an author are those builds which contains changes committed by the author.
0 (0%)
1 (100%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
0 (0% of all builds triggered)
0 (0% of all builds triggered)
Build Completed Code commits Tests
INTEXT › SIH1 › #37 8 months ago
GH-235: Fix a memory leak in HZ LeaderInitiator

According to the hazelcast team:
"The logic assumes that locks are generally acquired
& released in a fairly short time or hold a very long time without unlocking.
But in this case, is a bit different, it holds the lock for a long time,
but also does lock/unlock very frequently".

The previous implementation used the described logic,
first acquiring a lock and then doing frequent `tryLock/unlock`.
Doing this leads to
to grow without ever being cleaned thus leading to an `OutOfMemoryError` eventually.

* Rely on the `FencedLock.isLocked()` instead of frequent `tryLock/unlock`
* Fix `LeaderInitiatorTests` not to spawn 3 CP members since an unsafe mode is
enough to test the feature
106 passed
Build Completed Code commits Tests
Build Completed Code commits Tests