walterddr opened a new issue, #10864: URL: https://github.com/apache/pinot/issues/10864
Description === this specifically happens 1. when the server mailbox / v2 engine service port is dynamically configured; or 2. when server expansions happened without cluster restart when server restarts, 1. server updates the segment instance configuration with the new dynamically assigned config port 3. broker listens to the instance config change and updates its routing table with the newly assigned port. this is not happening for now. Follow up === one reported incident in https://apache-pinot.slack.com/archives/C011C9JHN7R/p1686141604049009?thread_ts=1685963058.774949&cid=C011C9JHN7R shows that the current work around is restart broker to let it pick up the new config. this indicates most likely the broker listener is not updating the config, server is updating fine -- 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.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
