Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 25 Jan 2013 21:59:13 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12606187.1346806151355.193207.1359151153002@arcas>
In-Reply-To: <JIRA.12606187.1346806151355@arcas>
References: <JIRA.12606187.1346806151355@arcas>
Subject: [jira] [Resolved] (ACCUMULO-751) Support Wire Compatibility
 (between bugfix releases)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs resolved ACCUMULO-751.
----------------------------------------

    Resolution: Fixed
    
> Support Wire Compatibility (between bugfix releases)
> ----------------------------------------------------
>
>                 Key: ACCUMULO-751
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-751
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master, thrift, tserver
>    Affects Versions: 1.4.0
>            Reporter: Mike Drob
>            Assignee: Christopher Tubbs
>            Priority: Critical
>              Labels: api, compatibility, versioning, wire, wireprotocol
>             Fix For: 1.5.0
>
>
> With the advent of the HA NameNode in HDFS, the need for planned Hadoop outages has greatly diminished. I believe that Accumulo should follow suit and eventually allow for no-outage upgrades.
> To support this feature, we would require wire compatibility between different versions so that the cluster can continue to function in a mixed state. There are already contingencies for master fail-over and tservers to leave/join the cluster, so I think this is a natural extension of that code.
> To accomplish this for bugfix releases should be trivial. I think it is only necessary to remove (or relax) the version check that happens when a tserver attempts to join. There are rarely (never?) changes to the thrift protocol between bugfix releases, so theoretically a 1.4.1 tserver is already compatible with a 1.4.0 master and vice versa.
> To maintain compatibility in the face of thrift protocol changes is certainly a harder challenge, which might be best reserved for a separate ticket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira