Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update java.adoc around client routing #1179

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −3
Open

Update java.adoc around client routing #1179

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/modules/clients/pages/java.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ The client is updated whenever the cluster version, partition groups, or CP grou

From {enterprise-product-name} 5.5, you can use any of the following cluster routing modes:

* **ALL_MEMBERS**
* **Client ALL_MEMBERS Routing**
+
The default mode, and is the equivalent of the legacy **Smart** client operation mode.
+
Expand All @@ -101,7 +101,7 @@ If <<configuring-direct-to-leader-routing, CP direct-to-leader routing>> is enab
license is present on your Enterprise cluster, then clients in this routing mode can use this to send CP operations
directly to group leaders wherever possible, even after leadership changes.

* **SINGLE_MEMBER**
* **Client SINGLE_MEMBER Routing**
+
In `SINGLE_MEMBER` cluster routing mode, clients only connect to one of the configured addresses. This is the equivalent of the legacy **Unisocket** client operation mode.
+
Expand All @@ -113,7 +113,7 @@ The single connected member behaves as a gateway to the other members.
When the client makes a request, the connected member redirects the request to the relevant member and
returns the response from that member to the client.

* **MULTI_MEMBER**
* **Client MULTI_MEMBER Routing**
+
This mode provides most of the functionality of `ALL_MEMBERS` mode over a single paritition group, falling back to the more restricted behavior
of `SINGLE_MEMBER` mode for members outside that partition group as follows:
Expand Down
Loading