Jackie-Jiang commented on PR #13668: URL: https://github.com/apache/pinot/pull/13668#issuecomment-2272257235
> If the previous consuming segment is still consuming and the server hosting that segment has not reacted to CONSUMING->ONLINE transition message for that segment, it means the queries are served with that consuming segment, so we should still report ingestion delays for that consuming segment. That is true, but we also want to remove the metrics immediately after all the records for the consuming segment is consumed because the next consuming segment is already tracked on a different server. I don't see a better way to handle this corner case. The assumption is that `CONSUMING -> ONLINE` state transition will arrive very soon, and the consuming segment will either be sealed or dropped. The delta is the message delivery time of custom message and state transition. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
