[ 
https://issues.apache.org/jira/browse/OAK-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389617#comment-16389617
 ] 

Marcel Reutegger commented on OAK-7316:
---------------------------------------

Proposed changes are:

* If there is no existing unused clusterId that matches the current working 
directory and MAC address, then:
** Use the lowest unused {{clusterId}} and update the {{instance}} (working 
directory), {{machine}} (MAC address) and {{info}} fields of the corresponding 
document in the {{clusterNodes}} collection to match the starting 
DocumentNodeStore
** Create a new {{clusterId}} when all existing ones are currently active

> Greedy ClusterNodeInfo
> ----------------------
>
>                 Key: OAK-7316
>                 URL: https://issues.apache.org/jira/browse/OAK-7316
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10
>
>
> The {{ClusterNodeInfo}} is responsible for assigning a {{clusterId}} to a 
> DocumentNodeStore on startup. The current implementation uses the lowest MAC 
> address available on the system and the working directory as information to 
> reuse a previously assigned {{clusterId}}. This ensures a DocumentNodeStore 
> gets the same {{clusterId}} after a restart.
> For static deployments this works fine, but become a problem when deployments 
> are more dynamic. Consider a cluster deployed on container infrastructure. 
> Scaling the application may mean cluster nodes are added or removed over time 
> and deployed on various types of machines depending on current load and 
> required resources. Over time more and more unused {{clusterIds}} would exist 
> and and bloat underlying documents in the DocumentStore.
> This issue proposes a more greedy algorithm when a {{clusterId}} is assigned 
> to a DocumentNodeStore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to