Discussion:
Failed to fetch parquet metadata after 15000ms
karthik.R
2018-10-08 06:50:30 UTC
Permalink
Hi,
I am frequently getting below exception when running a query in drill 1.14.
Could you please help what option to set to increase this timeout?

Waited for 15000ms , but tasks for 'Fetch parquet metadata' are not
complete. Total runnable size 4 , parallelism 4


My parquet files present in s3 location with 5 parquet file partitions.

Please help
Khurram Faraaz
2018-10-08 17:55:00 UTC
Permalink
Hi Karthik,

You can try setting the session/system option, exec.queue.timeout_millis to
a higher value, the default is 300000

Thanks,
Khurram
Post by karthik.R
Hi,
I am frequently getting below exception when running a query in drill 1.14.
Could you please help what option to set to increase this timeout?
Waited for 15000ms , but tasks for 'Fetch parquet metadata' are not
complete. Total runnable size 4 , parallelism 4
My parquet files present in s3 location with 5 parquet file partitions.
Please help
Abhishek Girish
2018-10-11 03:21:12 UTC
Permalink
Hey Karthik,

This is a bug and there are a few JIRAs to track this and one of those is
DRILL-5788 <https://issues.apache.org/jira/browse/DRILL-5788>. It's likely
because of a hard-coded default for the timeout which is sometimes not
sufficient. Can you please update the JIRA with your findings, which can
help resolving the issue?

Regards,
Abhishek
Post by karthik.R
Hi,
I am frequently getting below exception when running a query in drill 1.14.
Could you please help what option to set to increase this timeout?
Waited for 15000ms , but tasks for 'Fetch parquet metadata' are not
complete. Total runnable size 4 , parallelism 4
My parquet files present in s3 location with 5 parquet file partitions.
Please help
Loading...