-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Enable RemoteClusterService
client features on search nodes by default for CPS
#132553
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.
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
Enable RemoteClusterService
client features on search nodes by default for CPS
#132553
Conversation
For CPS in serverless we do not want to support RemoteClusterService client features on non-search nodes. This PR checks if stateless is enabled, and if so requires the node to have the search role to use RemoteClusterService client features. If stateless is disabled the check is only for the remote cluster client role, as is currently done today. Resolves: ES-12597.
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor comment. Also, you need to update the usage in TransportGetProjectTagsAction
on the stateless side to avoid breaking serverless build.
server/src/test/java/org/elasticsearch/transport/RemoteClusterServiceTests.java
Outdated
Show resolved
Hide resolved
On the tech design doc, IIUC, Henning suggested enabling remote cluster client by default for search nodes. Is this something we want to have? If so, is it going to be a separate PR? |
Yes, you are correct, I needed to adjust the logic in
I added linked PR 4355 to address this. |
RemoteClusterService
client features on non-search nodes for CPSRemoteClusterService
client features on search nodes by default for CPS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The new enforcement makes sense to me.
For CPS in serverless we do not want to support
RemoteClusterService
client features on non-search nodes that do not explicitly have the remote cluster client role set. This PR checks if stateless is enabled, and if so requires the node to have the search node role to useRemoteClusterService
client features if the remote cluster client role is not set. If stateless is disabled the check is only for the remote cluster client role, as is currently done today.Resolves: ES-12597.