ISPN-13982: Add note about explicitly setting BASIC intelligence for accessing internal and hidden cluster topology
#10200
Conversation
dfitzmau
added
the
Documentation
| @@ -5,6 +5,11 @@ Hot Rod clients use intelligence mechanisms to efficiently send requests to {bra | |||
| .`BASIC` intelligence | |||
| Clients do not receive topology change events for {brandname} clusters, such as nodes joining or leaving, and use only the list of {brandname} Server network locations that you add to the client configuration. | |||
|
|
|||
| [NOTE] | |||
| ==== | |||
| If a client from a remote cluster wants to connect with a {hr_name}} client in your local {brandname} cluster, set your client to use `BASIC` intelligence. This ensures that the remote client can send a request to your {brandname} cluster without experiencing client failover. | |||
There was a problem hiding this comment.
I'm sorry, but it isn't clear what you want to say here.
There was a problem hiding this comment.
the only reason why using BASIC is that the client is behind a Proxy/NAT/LB and does not have the ability to use the physical IP addresses provided by TOPOLOGY_AWARE
Or don't want to use it and rely only on the configured list (and accept the drawbacks)
If you meant the failover for XSite this is a different story and ISPN-13248 is about XSite config
There was a problem hiding this comment.
Hi @pruivo . My apologies. I received further info and I updated the content. More accurate?
dfitzmau
force-pushed
the
ISPN-13248
branch
2 times, most recently
from
122bfe3
to
261b7a5
Compare
|
|
||
| .`BASIC` intelligence | ||
| Clients do not receive topology change events for {brandname} clusters, such as nodes joining or leaving, and use only the list of {brandname} Server network locations that you add to the client configuration. | ||
|
|
||
| [NOTE] | ||
| ==== | ||
| Enable `BASIC` intelligence to expose a hidden IP address for a {hr_name} client that sent a request to a remote server. |
There was a problem hiding this comment.
Enable ... to use the client configuration only if the server cluster should not send back the topology as it is internal and hidden to the client. Examples are LoadBalancer, NAT, Proxy or OpenShift environment.
There was a problem hiding this comment.
Thanks, @wfink . I updated the content based on your feedback. Please let me know what you think.
dfitzmau
changed the title
BASIC intelligence for receiving remote client requestsBASIC intelligence for accessing internal and hidden cluster topology
|
merged! thanks @dfitzmau |
dfitzmau
changed the title
BASIC intelligence for accessing internal and hidden cluster topologyBASIC intelligence for accessing internal and hidden cluster topology
JIRA: https://issues.redhat.com/browse/ISPN-13982