Add destroy intention (soft destroy) for ILock about hazelcast

[flozano]

I think this would be a great feature, please +1 it.

[mmedenjak]

As the ILock implementation has been replaced with a raft implementation in 4.0, the difficulty for this enhancement has increased. Still, it is possible.

[metanet]

CP Subsystem already allows you to destroy locks, or actually any CP data structure. The only limitation is, once you destroy a CP data structure, you cannot reuse it before also destroying and restarting the underlying CP group.

https://docs.hazelcast.org/docs/3.12.6/manual/html-single/index.html#cp-subsystem

If you call the DistributedObject.destroy() method on a CP data structure proxy, that data structure is terminated on the underlying CP group and cannot be reinitialized until the CP group is force-destroyed. For this reason, please make sure that you are completely done with a CP data structure before destroying its proxy.

[prasanthnath]

This is indeed be a very helpful feature. We have a scenario where we create locks on the fly but could not destroy them after the usage as we may have to reuse the lock again. As they are not getting destroyed, we are getting OOM after a period of time. This is forcing us to do a periodic restart of Hazelcast servers.