mapshen commented on issue #7850: URL: https://github.com/apache/pinot/issues/7850#issuecomment-999826256
> > The consumption catch-up wait time leads to the split views described at the beginning, doesn't it? That's why we are have these conversations. > > Not really. The server doesn't serve queries until consumption catch-up wait is over. So all queries go to the other server which has not been restarted and has ingested the latest stream events. It does lead to split views in our experiments. As you mentioned in https://github.com/apache/pinot/issues/7274, the time threshold doesn't guarantee the server will be all caught up when the wait is over. > Realtime consumption status checker is used at startup time in Pinot Server to define a catch-up period in which no query execution happens and stream consumers try to catch up to the latest messages available in different streams. The current realtime consumption status checker defines a time threshold for startup consumption. When the wait time after Pinot Server starts up passes that time threshold, the status checker returns ServiceStatus.GOOD. -- 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
