Remove notion of v1 and v2 discovery services #1994
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jackwaudby
force-pushed
the
2024-12-one-discovery-service
branch
from
990dbbc to
01eda91
Compare
|
This PR includes documentation updates Updated pages: |
| @@ -9,25 +9,6 @@ This information is necessary to connect to the servers, run the discovery proto | |||
|
|
|||
| Neo4j provides several mechanisms for cluster members to discover each other and form a cluster based on the configuration and the environment in which the cluster is running, as well as the version of Neo4j being used. | |||
|
|
|||
There was a problem hiding this comment.
Suggested change
| [IMPORTANT] | |
| ==== | |
| In Neo4j 5.23, a new discovery service was introduced. | |
| It is very crucially important to switch to the the new version before you start using Neo4j 2025.01. | |
| See link:https://neo4j.com/docs/operations-manual/5/clustering/setup/discovery/[the guide for the Neo4j 5.x series] for more information. | |
| ==== | |
There was a problem hiding this comment.
I'd still be inclined to remove the notion of v2 here
jackwaudby
commented
Dec 23, 2024
| @@ -9,25 +9,6 @@ This information is necessary to connect to the servers, run the discovery proto | |||
|
|
|||
| Neo4j provides several mechanisms for cluster members to discover each other and form a cluster based on the configuration and the environment in which the cluster is running, as well as the version of Neo4j being used. | |||
|
|
|||
There was a problem hiding this comment.
I'd still be inclined to remove the notion of v2 here
| @@ -9,25 +9,6 @@ This information is necessary to connect to the servers, run the discovery proto | |||
|
|
|||
| Neo4j provides several mechanisms for cluster members to discover each other and form a cluster based on the configuration and the environment in which the cluster is running, as well as the version of Neo4j being used. | |||
|
|
|||
There was a problem hiding this comment.
Suggested change
| In Neo4j 5.23 a new discovery service was introduced. | |
| It is crucial to switch to this new version before you start using Neo4j 2025.01. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes all mention of v1 and v2 discovery services. We update all configurations and setup guides to reflect there is now one discovery service with 2 settings:
dbms.cluster.endpointsdbms.cluster.discovery.resolver_type