Skip to content

Conversation

JeremyDahlgren
Copy link
Contributor

@JeremyDahlgren JeremyDahlgren commented Aug 7, 2025

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 use RemoteClusterService 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.

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.
@JeremyDahlgren JeremyDahlgren requested a review from ywangd August 7, 2025 21:40
@JeremyDahlgren JeremyDahlgren added >non-issue :Distributed Coordination/Network Http and internode communication implementations Team:Distributed Coordination Meta label for Distributed Coordination team v9.2.0 labels Aug 7, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

Copy link
Member

@ywangd ywangd left a 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.

@ywangd
Copy link
Member

ywangd commented Aug 8, 2025

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?

@elasticsearchmachine elasticsearchmachine added the serverless-linked Added by automation, don't add manually label Aug 8, 2025
@JeremyDahlgren
Copy link
Contributor Author

JeremyDahlgren commented Aug 8, 2025

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 ensureClientIsEnabled() to enable the client features if in stateless on a search node.

... Also, you need to update the usage in TransportGetProjectTagsAction on the stateless side to avoid breaking serverless build.

I added linked PR 4355 to address this.

@JeremyDahlgren JeremyDahlgren changed the title Disable RemoteClusterService client features on non-search nodes for CPS Enable RemoteClusterService client features on search nodes by default for CPS Aug 8, 2025
Copy link
Member

@ywangd ywangd left a 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.

@JeremyDahlgren JeremyDahlgren merged commit 9f5908e into elastic:main Aug 11, 2025
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Coordination/Network Http and internode communication implementations >non-issue serverless-linked Added by automation, don't add manually Team:Distributed Coordination Meta label for Distributed Coordination team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants