Currently, in an oak-cluster when (e.g.) one oak-client stops renewing its lease (ClusterNodeInfo.renewLease()), this will be eventually noticed by the others in the same oak-cluster. Those then mark this client as inactive and start recoverying and subsequently removing that node from any further merge etc operation.
Now, whatever the reason was why that client stopped renewing the lease (could be an exception, deadlock, whatever) - that client itself still considers itself as active and continues to take part in the cluster action.
This will result in a unbalanced situation where that one client 'sees' everybody as active while the others see this one as inactive.
If this ClusterNodeInfo state should be something that can be built upon, and to avoid any inconsistency due to unbalanced handling, the inactive node should probably retire gracefully - or any other appropriate action should be taken, other than just continuing as today.
This ticket is to keep track of ideas and actions taken wrt this.