dang-stripe opened a new issue, #16457: URL: https://github.com/apache/pinot/issues/16457
https://github.com/apache/pinot/pull/10466 introduced a new default broker behavior to mark segments unavailable after a timeout set by `pinot.broker.new.segment.expiration.seconds` (defaults to 5 minutes). We hit query failures when new segment ingestion coincided with a table rebalance that delayed the newly ingested segments from going online in 5 minutes. The segments were then marked as routable by the broker and queries failed with "unavailable segments". There's no way to turn this behavior off aside from increasing `pinot.broker.new.segment.expiration.seconds` to a very high value. We'd like to be able to turn this off expiration behavior off completely so it reverts to the old behavior where the segment will be excluded from routing but not marked as unavailable until one of the segment replicas comes online. https://github.com/apache/pinot/blob/45389974f6fad5a5f35b074d06063673112e8dc2/pinot-broker/src/main/java/org/apache/pinot/broker/routing/instanceselector/BaseInstanceSelector.java#L186 -- 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]
