Hi Charles, Thanks for the suggestions — that definitely helps. To answer your questions:
* I’ve increased the Java heap, with the initial heap set to 8 GB and the max heap set to 32 GB. * The Drill cluster currently consists of 3 Drill nodes. * The data is stored in Parquet format. Despite these settings, I’m still running into the immediate query issues, which is why I wanted to confirm whether there are additional tuning recommendations you’d suggest around fragments or parallelization. Based on your feedback, I’ll also look into further breaking up the Parquet files to improve parallel execution, depending on the use case. Regarding the UI, that makes sense. I’ll avoid using the Drill UI for large result sets and instead plan to connect Drill to a proper UI like Apache Superset or pull results via JDBC when working with queries returning 1M+ records. Thanks again for the guidance — really appreciate it. Best regards, Anupam ________________________________ From: Charles Givre <[email protected]> Sent: Friday, January 9, 2026 2:06 AM To: [email protected] <[email protected]> Subject: Re: Issue with Distributed Query Execution and OutOfMemoryError in Apache Drill CAUTION: External Sender. Please do not click on links or open attachments from senders you do not trust.
