[jira] [Updated] (DRILL-7223) Make the timeout in TimedCallable a configurable boot time parameter

["Arina Ielchiieva (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arina Ielchiieva updated DRILL-7223:
------------------------------------
    Fix Version/s:     (was: 1.17.0)
                   1.18.0

> Make the timeout in TimedCallable a configurable boot time parameter
> --------------------------------------------------------------------
>
>                 Key: DRILL-7223
>                 URL: https://issues.apache.org/jira/browse/DRILL-7223
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.16.0
>            Reporter: Aman Sinha
>            Assignee: Boaz Ben-Zvi
>            Priority: Minor
>             Fix For: 1.18.0
>
>
> The [TimedCallable.TIMEOUT_PER_RUNNABLE_IN_MSECS|https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/store/TimedCallable.java#L52] is currently an internal Drill constant defined as 15 secs. This has been there from day 1 of the introduction. Drill's TimedCallable implements the Java concurrency's Callable interface to create timed threads. It is used by the REFRESH METADATA command which creates multiple threads on the Foreman node to gather Parquet metadata to build the metadata cache.
> Depending on the load on the system or for very large scale number of parquet files (millions) it is possible to exceed this timeout.  While the exact root cause of exceeding the timeout is being investigated, it makes sense to make this timeout a configurable parameter to aid with large scale testing. This JIRA is to make this a configurable bootstrapping option in the drill-override.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)