Pratheek Shetty
08/11/2025, 9:43 AMpinot.broker.enable.query.cancellation=true and slow-query logging.
• Monitored broker/server metrics — no memory spikes, CPU high during issue.
• Total partitions for this table: 10, total servers: 10.
Questions:
1. Has anyone seen Pinot servers becoming unresponsive purely from a large scan, even when heap/GC are fine?
2. Is there a recommended way to limit docs scanned per query or abort queries early when scan is excessive?
3. Any known fixes/tunings in versions >1.3.0 for preventing one heavy query from starving all server threads?
4. Would increasing server query threads or adjusting segment assignment help, or just postpone the problem?
Any insights, patterns, or configs we should look at would be appreciated.Mayank
Pratheek Shetty
09/06/2025, 6:44 AMMayank
Priyen Patel
09/19/2025, 12:45 AM