Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7A3610C92 for ; Tue, 27 May 2014 21:46:37 +0000 (UTC) Received: (qmail 16571 invoked by uid 500); 27 May 2014 21:46:37 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 16488 invoked by uid 500); 27 May 2014 21:46:37 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 16480 invoked by uid 99); 27 May 2014 21:46:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 May 2014 21:46:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.217.177 as permitted sender) Received: from [209.85.217.177] (HELO mail-lb0-f177.google.com) (209.85.217.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 May 2014 21:46:31 +0000 Received: by mail-lb0-f177.google.com with SMTP id s7so5326678lbd.36 for ; Tue, 27 May 2014 14:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=hHll3GnMU1Wn/akKGlf15LDFmz7vRCC0wdGEpy0MIoM=; b=voO2oDZvk2pe2pVQtpM9tQjV2mdMfxiS4onIswSi5NOpYlKqdoY/cgHs/5YpDO7Vf5 8918CEU5jnvIWDHB9BOuZNYqTCygwUZh/EQvTFhqP59cfSVYJse9+GvaDQWuNGorgMdf 4pEUKg5qNRHhPlt74G+0BYgCxEW83eKocxDpjv6i0VsI967ALbZXu93wgzoUnQvoW9Wc /tZevdXr4oAoOW0pF3jgSl9gdHwU5GMDyrrMshYOZow9F/NH53Qwq7S3giMO8WEZePoz 8MTgQ0Ml+NplOKIU3YxwRbgW8eY2xs29qQXjJsk+pn0Whi7J/r/2cjXrRFogMjfOdoSW EEuA== MIME-Version: 1.0 X-Received: by 10.112.61.102 with SMTP id o6mr5079823lbr.74.1401227170297; Tue, 27 May 2014 14:46:10 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.152.2.38 with HTTP; Tue, 27 May 2014 14:46:10 -0700 (PDT) In-Reply-To: References: Date: Tue, 27 May 2014 14:46:10 -0700 X-Google-Sender-Auth: A4ogz5GyBRk0Nh0uSbMjv2fPhtg Message-ID: Subject: Re: Gathering opinions and recommendations From: Stack To: HBase Dev List Content-Type: multipart/alternative; boundary=e89a8f642ff4bc3e5b04fa689f7f X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f642ff4bc3e5b04fa689f7f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > The 'stable' is still 0.94.19? Lets fix this. 0.98.3 becomes new 'stable'? On Tue, May 27, 2014 at 2:40 PM, Enis S=C3=B6ztutar wrote= : > Inlined. > ... > > > One more question: future upgrade from 0.96 -> 1.0 and 0.98 -> 1.0? > > > Rolling or not? > > > > 0.96 -> 1.0 probably won't be supported unless there is explicit interest > and work for it. I doubt that will happen. The reason is hfile v3 is > default in 1.0, but 0.96 code base cannot read hfile v3 files. This means > that rolling restarts is tricky because if a new server writes a new hfil= e, > old servers cannot read this, the region won't be opened and will keep > bouncing until it hits a new server. In theory it should work, but I won'= t > recommend doing it. > > Our book actually says this http://hbase.apache.org/book.html#d3219e3534 (Y= ah!). St.Ack --e89a8f642ff4bc3e5b04fa689f7f--