Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 8 Apr 2016 23:29:25 +0000 (UTC)
From: "Parth Chandra (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12957180.1460112641000.181375.1460158165494@Atlassian.JIRA>
In-Reply-To: <JIRA.12957180.1460112641000@Atlassian.JIRA>
References: <JIRA.12957180.1460112641000@Atlassian.JIRA>
 <JIRA.12957180.1460112641036@arcas>
Subject: [jira] [Commented] (DRILL-4596) Drill should do version check among
 drillbits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DRILL-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233145#comment-15233145 ] 

Parth Chandra commented on DRILL-4596:
--------------------------------------

The common use case for having drillbits of different versions is for performing rolling upgrades, especially in a production environment. You never upgrade all the nodes in a cluster. You take a set of nodes offline, upgrade them, bring them online, repeat until all nodes are upgraded. During the upgrade, processes that require the older version of (any) software running continue to run as before.


> Drill should do version check among drillbits
> ---------------------------------------------
>
>                 Key: DRILL-4596
>                 URL: https://issues.apache.org/jira/browse/DRILL-4596
>             Project: Apache Drill
>          Issue Type: New Feature
>    Affects Versions: 1.6.0
>            Reporter: Arina Ielchiieva
>            Assignee: Arina Ielchiieva
>             Fix For: Future
>
>
> Before registering new drillbit in zookeeper, we should do version check, and make sure all the running drillbits are in the same version.
> Using drillbits of different version can lead to unexpected results.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)