[
https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated JCR-2857:
--------------------------------
Attachment: jcr-2857.patch
This patch is a first version of the node id factory. The default behavior is
to generate random id like now. If the system property
jackrabbit.sequentialNodeId is set, node ids are generated sequentially. The
next node id is stored in a file nodeId.properties. This file is updated every
128 generated node ids for performance reason. If the process is killed, up to
128 node ids are lost. The counter only covers the lower 64 bits, the 64 most
significant bits (msb) are fixed (to 0 unless otherwise specified). If the
system property jackrabbit.sequentialNodeId contains a '/', then the next id is
read from there. Example: 1/0 means the msb is set to 1 and the lsb to 0. In
this way, sequential node ids can be used in a cluster (each cluster node needs
it's own msb).
> Support sequential (non-random) node ids
> ----------------------------------------
>
> Key: JCR-2857
> URL: https://issues.apache.org/jira/browse/JCR-2857
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Attachments: jcr-2857.patch
>
>
> Currently, node ids are generated using a (cryptographically secure pseudo-)
> random number generator. This has a many advantages (easy to implement, easy
> to merge nodes from multiple repositories or cluster nodes), but is a
> performance bottleneck for large repositories.
> In addition to generating random node ids, Jackrabbit should support
> generating sequential node ids.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
