[ https://issues.apache.org/jira/browse/DRILL-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241185#comment-15241185 ]
John Omernik commented on DRILL-4604: ------------------------------------- So this confused me a bit, so I did some testing. There must be configuration items stored in the Zookeeper information about the cluster. For example: Default setting for exec.queue.enable is false. I validated this on my cluster. I changed it, as an admin user, with ALTER SYSTEM SET `exec.queue.enable` = true; This returned correctly and select * from sys.options; showed the value as changed. Note, I did not update ANY configs on ANY drill bits, just altered the setting in the cluster. Then I shutdown all my drill bits, and then restarted them. Thus, there is no place this setting was set in configuration, it was just changed with ALTER SYSTEM (and thus I am assuming it was changed in Zookeeper). With the restarted cluster, the setting persisted, (it was set to true after restart). So, there must be a configuration store in Zookeeper that allowed this setting to persist. John > Generate warning on Web UI if drillbits have different versions > --------------------------------------------------------------- > > Key: DRILL-4604 > URL: https://issues.apache.org/jira/browse/DRILL-4604 > Project: Apache Drill > Issue Type: Improvement > Affects Versions: 1.6.0 > Reporter: Arina Ielchiieva > Assignee: Arina Ielchiieva > Fix For: 1.7.0 > > > Display drillbit version on web UI. If any of drillbits version doesn't match > with current drillbit, generate warning. > Screenshots - TBA. -- This message was sent by Atlassian JIRA (v6.3.4#6332)