piby180 commented on issue #12888:
URL: https://github.com/apache/pinot/issues/12888#issuecomment-2161844064
@vineethvp @xiangfu0
Looks like I finally hit the jackpot on this issue after 2 months.
I have added the following to pinot-server-headless and
pinot-broker-headless services and the error seems to disappear.
```
spec:
publishNotReadyAddresses: true
```
From Kubernetes docs
> publishNotReadyAddresses indicates that any agent which deals with
endpoints for this Service should disregard any indications of ready/not-ready.
The primary use case for setting this field is for a StatefulSet's Headless
Service to propagate SRV DNS records for its Pods for the purpose of peer
discovery. The Kubernetes controllers that generate Endpoints and EndpointSlice
resources for Services interpret this to mean that all endpoints are considered
"ready" even if the Pods themselves are not. Agents which consume only
Kubernetes generated endpoints through the Endpoints or EndpointSlice resources
can safely assume this behavior.
https://kubernetes.io/docs/reference/kubernetes-api/service-resources/service-v1/#ServiceSpec
@vineethvp Could you test it on your end if adding
`publishNotReadyAddresses: true` to pinot-broker-headless and
pinot-server-headless fix the issue?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
