You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by "ankitsultana (via GitHub)" <gi...@apache.org> on 2023/04/04 18:28:03 UTC

[GitHub] [pinot] ankitsultana commented on issue #10539: Segment Pruning does not respect query timeout

ankitsultana commented on issue #10539:
URL: https://github.com/apache/pinot/issues/10539#issuecomment-1496415897

   The issue regarding timeout based pre-emption is general. For supporting interrupts we'll have to add interrupt checks everywhere so it is not limited to `SegmentPruner`.
   
   I haven't checked Guava `TimeLimiter` either but I don't think it would be able to stop an arbitrary function unless the function itself supports interruption (by checking Thread interrupt status). For context even Future methods like `Future.cancel` only set the interrupt flag and don't actually "cancel" any arbitrary function.
   
   The thing that is interesting though is why the segment pruner is taking this long. Can you share more context about the issue: how many segments you have, what's the query you are trying, etc.
   
   I presume it is the `ColumnValueSegmentPruner` which is taking a long time.


-- 
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