Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3126410123 for ; Mon, 16 Feb 2015 20:22:33 +0000 (UTC) Received: (qmail 64552 invoked by uid 500); 16 Feb 2015 20:22:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 64519 invoked by uid 500); 16 Feb 2015 20:22:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 64166 invoked by uid 99); 16 Feb 2015 20:22:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2015 20:22:12 +0000 Date: Mon, 16 Feb 2015 20:22:12 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-3598) Address varied file versions by servers over RPC layer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Josh Elser created ACCUMULO-3598: ------------------------------------ Summary: Address varied file versions by servers over RPC layer Key: ACCUMULO-3598 URL: https://issues.apache.org/jira/browse/ACCUMULO-3598 Project: Accumulo Issue Type: Sub-task Components: tserver Reporter: Josh Elser Fix For: 1.7.0 There's an issue of handling newer versions of RFile and WALs in the middle of a rolling restart. 1. Server1 is restarted as the new version 2. Server1 writes some new data 3. Server1 dies 4. Server2 (still old version) gets the tablets from Server1 We need to ensure that there is control to limit the new software from writing out new versions of persistent files while there are still old versions of the software participating in the instance. It's similar to finalizing an upgrade: after we're sure that all of the servers have been upgraded and are functioning well, we can flip them over to using new messages/serialization that the old versions aren't aware of. This problem gets much easier after we adopt Thrift/PB for serializing things because both of those can naturally read newer versions of messages they know about, ignoring the new fields. Ideally, we should define an API which rolling restart (ACCUMULO-1454) can leverage, but there are many ways we could go about the "feature". -- This message was sent by Atlassian JIRA (v6.3.4#6332)