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

Fix: Publish DNS for not-ready pods via the headless service #115

Merged
merged 1 commit into from
Dec 14, 2023

Conversation

mrIncompetent
Copy link
Contributor

For clustering/discovery purpose, we use the headless service of the StatefulSet today. It'll provide a DNS entry for every pod of the StatefulSet. Qdrant pods use this specific DNS name as --uri, so that's what's communicated to each peer. By default the service will only provide DNS name when the pod is ready. So if a pod is not ready, other peers cannot reach it. But we should change the service to always provide DNS for a pod, regardless it's readiness, using .spec.publishNotReadyAddresses=true to allow cluster-internal traffic.

For clustering/discovery purpose, we use the headless service of the StatefulSet today. It'll provide a DNS entry for every pod of the StatefulSet. Qdrant pods use this specific DNS name as --uri, so that's what's communicated to each peer. By default the service will only provide DNS name when the pod is ready. So if a pod is not ready, other peers cannot reach it. But we should change the service to always provide DNS for a pod, regardless it's readiness, using .spec.publishNotReadyAddresses=true to allow cluster-internal traffic.
@bashofmann bashofmann merged commit 3e74edf into main Dec 14, 2023
1 check passed
@bashofmann bashofmann deleted the publish-node-ready-addresses branch December 14, 2023 10:34
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.

3 participants