docs(ha): the bolt:/grpc: server-list fields, and when a client routing address is withheld - #441
Merged
Merged
Conversation
…ing address is withheld The object form of arcadedb.ha.serverList gained bolt: (#5002) and grpc: (#6091), neither of which was documented outside the code. A new "Client Routing Ports" section says what they are for and the sentence that matters operationally: declare them whenever your nodes do not all listen on the same port for that protocol, because the fallback derives a peer's address from this node's port. It also documents what #6183 changed: when two peers derive to the same address - nodes that share a host and differ only by port - neither is advertised, because two listening sockets cannot own one host:port, and nothing at all is advertised when the leader is one of them. BOLT then answers ROUTE with itself as READ and ROUTE only. arcadedb.grpc.port is now a registered server setting, so unlike the other grpc.* keys it is resolved from environment variables too.
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Companion to ArcadeData/arcadedb#6187 (issue ArcadeData/arcadedb#6183, item 3).
The object form of
arcadedb.ha.serverListgainedbolt:when #5002 added the BOLT routing table andgrpc:when #6091 made a gRPC refusal name a dialable leader. Onlybolt:had ever been mentioned in the docs, and only in passing on the BOLT page; the server-list reference itself listed neither.how-to/operations/ha.adoc:boltandgrpcrows in the object-form field table, a note that neither has a positional equivalent, and a new Client Routing Ports section carrying the sentence that matters operationally - declare them whenever your nodes do not all listen on the same port for that protocol, because the fallback derives a peer's address from this node's own port. The section also documents what Follow-ups from #6091: a derived routing address can point a client back at the refusing node, and only graphBatchLoad names the leader arcadedb#6183 changed: when two peers derive to the same address, neither is advertised (two listening sockets cannot own onehost:port), and nothing is advertised at all when the leader is one of them.how-to/connectivity/bolt.adoc: the existing heterogeneous-ports note gains what a driver now sees in that case - ROUTE answers with this node as READ and ROUTE only, exactly as mid-election, and declaringboltis what restores a WRITE entry.reference/settings.adoc:grpc.portis a registered server setting since v26.9.1, so unlike the othergrpc.*keys it is resolved from environment variables and appears in the settings API; the paragraph claiming otherwise for all of them is corrected.