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.

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

DiscoveryNodeManager to not return Coordinator/Resource Manager if not allowed by NodeStatusService #18473

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

swapsmagic
Copy link
Contributor

@swapsmagic swapsmagic commented Oct 10, 2022

In some mysterious conditions, we noticed coordinators are showing up in discovery service, and this lead to a bad state where resource managed start failing getResourceGroupInfo call due to incosistency in the coordinator count. we want to mitigate it by removing this checks which are no longer needed given NodeStatusService should filter them.

Redoes the old PR #18086 which got reverted: #18193 due to an issue of active coordinators were not found during verifier run.

Test plan - Verifier run

== NO RELEASE NOTE ==

…t allowed by NodeStatusService

In some mysterious conditions, we noticed coordinators are showing up in discovery service, and this lead to
a bad state where resource managed start failing getResourceGroupInfo call due to incosistency in the coordinator
count. we won't to mitigate it by removing this checks which are no longer needed given NodeStatusService should filter
them.
@swapsmagic swapsmagic merged commit 5daa2fe into prestodb:master Oct 11, 2022
@swapsmagic swapsmagic deleted the disallow_disagg_old_nodes branch October 11, 2022 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants