[
https://issues.apache.org/jira/browse/DRILL-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136737#comment-14136737
]
Aditya Kishore commented on DRILL-1427:
---------------------------------------
There are two way this can be handled.
# Disable the storage plugin instance if an error is encountered at the time of
initialization. This would require a manual intervention to re-enable the
plugin after correcting the error.
# Keep retrying the setting up the plugin instance every time and continue
ignoring until the error goes away. This will slow down all the queries until
the problem is resolved.
I am inclined to go with choice #1.
> Failure to initialize storage plug-in results in complete failure of
> drill-bit initialization
> ---------------------------------------------------------------------------------------------
>
> Key: DRILL-1427
> URL: https://issues.apache.org/jira/browse/DRILL-1427
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Drill
> Affects Versions: 0.5.0
> Environment: Observed on CentOS 6.4 on AWS instances
> Reporter: David Tucker
> Assignee: Aditya Kishore
>
> The storage plug-in configuration screen identifies when a plug-in fails to
> initializes (eg the Hive server is down) and will leave the plug-in disabled
> (or fail to creat it altogether). However, if a configured storage plug-in
> is not on line when the drill-bit is launched, all attempts at interactive
> queries (via sqlline or ODBC) fail to proceed. The impression left with the
> user is that the drill-bit is completely off-line.
> To reproduce:
> 1. configure Hive storage plug-in and execute simple queries
> 2. shut down drill-bit
> 3. shut down Hive server
> 4. re-launch the drill-bit
> 5. launch sqlline
> ... no connection will be established, no queries will be possible
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
