[GitHub] [pinot] sajjad-moradi commented on issue #10460: forceCommit, and maybe segment commit in general, might pick an unhealthy/lagging winner

["sajjad-moradi (via GitHub)" <gi...@apache.org>]

sajjad-moradi commented on issue #10460:
URL: https://github.com/apache/pinot/issues/10460#issuecomment-1483511426

   Subbu is correct. The reason was to immediately kick off the force commit. Having said that, I agree that since the wait time to find out the server with the highest ingested offset is short - around 3s - we can modify the force commit to function like time-based commit scenarios and select the winner with the highest offset.


-- 
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-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org