You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But this mapping doesn't actually match the underlying data. This is a different problem in Pinot where it's not always possible to express partitioning info used for the data in Pinot. But regardless of the cause, this log is way too high volume.
possible fixes:
change to DEBUG. Do we actually need this log?
should this ever log more than once per segment? shouldn't the online servers eventually match?
The text was updated successfully, but these errors were encountered:
Currently it is logged once per segment per assignment change (e.g. a new segment being pushed/deleted). We should aggregate them, and only log once for all segments
#11599 added https://github.com/apache/pinot/blame/master/pinot-broker/src/main/java/org/apache/pinot/broker/routing/segmentpartition/SegmentPartitionMetadataManager.java#L168-L172 for more logging. Internally, we're seeing this log show up almost 1B times per day over many tables.
My hypothesis is it's due to the fact that we have set
But this mapping doesn't actually match the underlying data. This is a different problem in Pinot where it's not always possible to express partitioning info used for the data in Pinot. But regardless of the cause, this log is way too high volume.
possible fixes:
The text was updated successfully, but these errors were encountered: