piby180 commented on issue #12888: URL: https://github.com/apache/pinot/issues/12888#issuecomment-2161694712
Hi @vineethvp 1. Pinot upgrade to 1.1.0 didn't help us. 2. We are still facing the issue but we have reduced the downtime window by optimally using probes especially startup probes. I have recently supported a PR to allow flexibility in adjusting probe settings. This was merged recently to pinot helm chart. On slack, I see quite a few users are experiencing this issue. The core issue is a server is ”marked“ ready by Pinot but it is not yet ”marked“ ready by kubernetes because readiness probe hasn't succeeded yet. Because of this, Pinot start sending traffic to the server but the server dns does not respond properly. Pinot needs to wait until the server dns endpoint is working again. cc @xiangfu0 @Jackie-Jiang -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
