Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F0E2E876 for ; Tue, 26 Feb 2013 07:33:56 +0000 (UTC) Received: (qmail 1306 invoked by uid 500); 26 Feb 2013 07:33:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 1253 invoked by uid 500); 26 Feb 2013 07:33:53 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 1223 invoked by uid 99); 26 Feb 2013 07:33:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 07:33:52 +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 (nike.apache.org: domain of aphawk@gmail.com designates 209.85.160.52 as permitted sender) Received: from [209.85.160.52] (HELO mail-pb0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2013 07:33:42 +0000 Received: by mail-pb0-f52.google.com with SMTP id ma3so2200567pbc.25 for ; Mon, 25 Feb 2013 23:33:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:message-id:in-reply-to:references:subject :x-mailer:mime-version:content-type; bh=g+TP6ob/cZTlc2ZvPdDaEa1GszKU0ZCpWk5nhcgo9SM=; b=jPs4+d2xrHL/4Hg0FAdXZH6ijJOudqBiasoht15SuH5fXUfSrn/uWVO9kBlOSo5w4k Jv7D4Dq7dmvJR0+fEMHLanNBpF57oEZFg+Xe52Yz1dG/447xTqI6sOWAyXQ6RCfgVy3r orj3VwcNBLPh6GSACr4EXCkh366E23DR7cyTWxqSmM0OeYAx2YDSyGDG8jdsCxYI1Ijm oEMgJB3bokhyQ4AxlkuGwGnr40Xfe7jee68vdMror527dIHtwgaOZtuY2VcZDPtqNnm2 hwRR3m1ZdLpy/NXM6yn+4RNDO9Dd+/108NRBWBYI5FHogeTKdPbDcJENWHk1oJSiJZNy 2LPw== X-Received: by 10.66.160.230 with SMTP id xn6mr411836pab.119.1361864001435; Mon, 25 Feb 2013 23:33:21 -0800 (PST) Received: from [10.7.245.144] ([202.55.20.10]) by mx.google.com with ESMTPS id x2sm518327paw.8.2013.02.25.23.33.18 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 25 Feb 2013 23:33:20 -0800 (PST) Date: Tue, 26 Feb 2013 15:33:15 +0800 From: Yusup Ashrap To: user@hbase.apache.org Message-ID: <857F1A1D10554F4E9CBFB6FCF557D1AD@gmail.com> In-Reply-To: References: <1360803001.75692.YahooMailNeo@web140601.mail.bf1.yahoo.com> <6670454D-5AE4-40BD-A5E2-43FA1D70E33B@gmail.com> Subject: Updating from 0.90.2 to 0.94 X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="512c653b_d34b6a8_2180" X-Virus-Checked: Checked by ClamAV on apache.org --512c653b_d34b6a8_2180 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline hi all, I am updating production cluster from 0.90.2 to 0.94 . My table's size is about 20TB+ . Scheduled update includes upgrading both hbase,hadoop version, and I am also changing user with which I start up both hadoop and hbase cluster from user "A" to user "B". It's production environment , so I wanted know what steps I should not miss regarding this upgrade. Table is kinda big and I don't have backup cluster to backup my data. I wanted to know will there be a data loss scenario if I rollback after having failed to upgrade. thanks. -- Best Regards Yusup Ashrap --512c653b_d34b6a8_2180--