You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "James Turton (Jira)" <ji...@apache.org> on 2022/09/21 12:55:00 UTC

[jira] [Updated] (DRILL-8314) Add support for automatically retrying and disabling broken storage plugins

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

James Turton updated DRILL-8314:
--------------------------------
    Summary: Add support for automatically retrying and disabling broken storage plugins  (was: Add support for automatically disabling broken storage plugins)

> Add support for automatically retrying and disabling broken storage plugins
> ---------------------------------------------------------------------------
>
>                 Key: DRILL-8314
>                 URL: https://issues.apache.org/jira/browse/DRILL-8314
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - Other
>    Affects Versions: 1.20.2
>            Reporter: James Turton
>            Assignee: James Turton
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Enabled storage plugins may malfunction for different reasons, e.g. they have been misconfigured or their remote data source has gone offline. Depending on the plugin's implementation, this could cause it to fail to return optimizer rules or register schemas. In some cases this can have a wider impact, e.g. unconditioned queries against the info schema will fail if a single plugin is failing in registerSchemas.
> Rather than us swallowing such errors and silently returning a subset of results, this Jira proposes a new feature controlled by two SYSTEM options that, when enabled, means that a broken plugin will still cause a query failure but it will also disable the broken plugin after a configurable number of attempts and inform the user that is has done so. Knowing what has just happened, the user can choose to reissue the query knowing that the broken plugin is now disabled or they might choose to investigate the problem affecting the broken plugin instead.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)