Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
In OAK-10281 a static ClusterNodeInfo.recoveryDelayMillis has been introduced. While not a drama, preferably we'd have it non static eg bound to some config/context or just DocumentNodeStore instead. This ticket is to revisit this static in the context of some broader refactoring that eg might also include the similarly static clock object. Several ideas were discussed in PR#1288 eg PR#1292 or PR#1301 that could serve as a basis for future discussions.