jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7316) Greedy ClusterNodeInfo
Date Tue, 03 Jul 2018 15:30:00 GMT

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

Marcel Reutegger commented on OAK-7316:

And the documentation update: http://svn.apache.org/r1834988

> 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, 1.9.6
> 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

View raw message