Today is Leonhard Euler’s birthday, and we’re celebrating by announcing a first Release Candidate for Neo4j 1.9, now available for download! This release includes a number of incremental changes from the last Milestone (1.9-M05). This release candidate includes the last set of features we’d love our community to try out, as we prepare Neo4j 1.9 for General Availability (GA).
Want to learn more about graph databases? Click below to get your free copy of O’Reilly’s Graph Databases ebook and discover how to use graph technologies for your application today.
Download My Ebook
|Google is celebrating Euler’s birthday with this Doodle.
Neo4j rings it in with a 1.9 Release Candidate!
Key changes since the last milestone are as follows:
The experimental mechanism for automatically assigning server ids based on the instance’s URI has been changed. The administrator must now explicitly set integer server ids in exactly the same manner as in 1.8.
We have removed an experimental feature introduced in earlier 1.9 milestones, which added the ability to specify a central cluster definition URI. This turned out to be underused and to introduce unneeded complexity.
It is now possible to introduce a new instance to the cluster to replace a failed one. This requires the new instance to have the same ID as the one that failed.
Cluster formation requires a majority of instances to be available, based on the instance count implied by initial_hosts
Fixes addressing cluster formation, when instances are concurrently started up
The cluster will explicitly deny instances from joining if they have a server_id that is already in use
As always with a release candidate, please download and examine this version thoroughly and help us spot anything that is amiss. We’re looking forward to the final 1.9 GA release in a short time.
Philip Rathle & The Neo4j Team