xiangfu0 opened a new issue, #15727: URL: https://github.com/apache/pinot/issues/15727
For a realtime table with >=2 replicas, the broker routing may hit any CONSUMING segment, which might cause user side to see inconsistent results due the consuming speed. I feel we should allow a definition from controller for the lead consuming server for a table partition, then the new routing strategy should always use this lead CONSUMING segment across all replicas and then always query this segment. -- 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
