Major Description
Currently intermediate nodes (two levels) in the version storage are initialized lazily. This works fine in a single cluster node deployment, but may become a problem when versionable nodes are created on multiple cluster nodes concurrently. A conflict will occur when two cluster nodes try to create the same intermediate nodes.
There should be an option for the initial content to pre-populate the version store with intermediate nodes to avoid those conflicts.