You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Jason Altekruse (JIRA)" <ji...@apache.org> on 2015/01/21 01:02:37 UTC
[jira] [Created] (DRILL-2048) Malformed drill stoage config stored
in zookeeper will prevent Drill from starting
Jason Altekruse created DRILL-2048:
--------------------------------------
Summary: Malformed drill stoage config stored in zookeeper will prevent Drill from starting
Key: DRILL-2048
URL: https://issues.apache.org/jira/browse/DRILL-2048
Project: Apache Drill
Issue Type: Bug
Reporter: Jason Altekruse
Assignee: Jason Altekruse
We noticed this problem while trying to test dev builds on a common cluster. When applying changes that added a field to the configuration of a storage plugin, the new format of the configuration would be persisted in zookeeper. When a different dev build that did not include the change set tried to be deployed on the same cluster the config stored in zookeeper would fail to parse and the drillbit would not be able to start. This is not system critical configuration so the drillbit should be able to still start with the plugin disabled.
This fix could also include changing the jackson mapper to allow ignoring unexpected fields in the configuration. This would give a little better chance for interoperability between future versions of Drill as we add new configuration options as necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)