sajjad-moradi commented on issue #11441: URL: https://github.com/apache/pinot/issues/11441#issuecomment-1701432966
If the goal is to catch consumption issues, as Subbu mentioned, freshness metric can be used. If the goal is to know how many rows are there in the table, using this metric is problematic. If one replica has consumption issue, the aggregated count divided by replica count shows an incorrect value, because the non-problematic replica(s) serve queries correctly, while the aggregate metric shows that there are less rows in the table. -- 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
