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 CB80810D4D for ; Mon, 11 Nov 2013 17:28:58 +0000 (UTC) Received: (qmail 53739 invoked by uid 500); 11 Nov 2013 17:28:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 53654 invoked by uid 500); 11 Nov 2013 17:28:43 -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 53646 invoked by uid 99); 11 Nov 2013 17:28:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Nov 2013 17:28:42 +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: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Nov 2013 17:28:33 +0000 Received: by mail-ve0-f177.google.com with SMTP id jz11so2357516veb.8 for ; Mon, 11 Nov 2013 09:28:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=qnBOrSq3/zuWaWOKrwCn6ZvnYRvIs4LrPCz0eUXXrO4=; b=Cqy3BemzCqbgB+3EIgLHSq/uM2uYcALE6PnXV5mNOCMK9EmHQMYd+V313+ARh21eQf nVwNQOcUwTCoF2X/N+6F3Ge0JBDh/U+UpmFrY94dupAKjzhUVbmygs3KBjx6PhFxuWQ/ 65SojUeB3aySgxNmxiQ7G9XS6Z4wIvm305rdJwyu/nRjrWYI+Zoqp/v4s0YD/64R45Mx jOt1M/9ntTB7lYKzS9T2rpEte2AFaPdzjSpraNLVsEHlEkHV2vMPhePpKB65V2U10Hwf x9Ww9gDs6qnZm6QJ8j2bIZm2u1nwmgShLk1fITSX63kEfPm2IPM1rD/0ujDxw2tfj3cm VPMQ== X-Gm-Message-State: ALoCoQkmkRWKyxlxmq7+2M2qQE2R7LlGvpr4iI9VWGwjq8bAKJKlhUdNY/tzbFHqaq/HmhefOBT8 X-Received: by 10.58.178.239 with SMTP id db15mr25270957vec.9.1384190892574; Mon, 11 Nov 2013 09:28:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.175.202 with HTTP; Mon, 11 Nov 2013 09:27:52 -0800 (PST) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Mon, 11 Nov 2013 12:27:52 -0500 Message-ID: Subject: Re: Migrate 0.94 to remote 0.96 To: user Content-Type: multipart/alternative; boundary=047d7b672a9674241c04eaea0e32 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b672a9674241c04eaea0e32 Content-Type: text/plain; charset=UTF-8 Sure! I will have 2 comments. 1) In the documentation, we expect user to have an existing cluster in 0.94 and to try to upgrade it. However, some might prefer to move the data to a new one to not risk the gold data, and migrate the new one. We might want to put some links on DistCP, CopyTable or others to help with with that. Also, it might be different versions of HDFS underneath (1.2 to 2.2, etc.) for might also tell them about the need to use hftp (I know, it's related to Hadoop and not HBase, but it took me some time to find the right command line). 2) -check should verify that compression codecs configured in the tables are available and working. Not required when migrating into the same cluster, but useful when you move the data and upgrade into another cluster. Apart from that (and some Yarn vs MapReduce challenges to get rowcounter working fine), everything else went very smoothly. JM 2013/11/11 Himanshu Vashishtha > Thanks for trying it out. > > Would be great to have your inputs/suggestions on making it more user > friendly JM. > > Himanshu > > > On Mon, Nov 11, 2013 at 5:44 AM, Jean-Marc Spaggiari < > jean-marc@spaggiari.org> wrote: > > > So, seems that it went well. The only thing is that I don't have snappy > on > > the new cluster so one table has 0 regions deployed, but expect that, > seems > > pretty "simple". Thanks again. > > > > > > 2013/11/10 Jean-Marc Spaggiari > > > > > Thanks Himanshu. I missed this section. So I will "simply" dump all > HDFS > > > files to huge disks, move them, restore them on the other side and run > > > hbase upgrade... It seems to be pretty easy. I will update this thread > > with > > > the result... > > > > > > JM > > > > > > > > > 2013/11/10 Himanshu Vashishtha > > > > > >> JM, > > >> > > >> Did you look at the upgrade section in the book, > > >> http://hbase.apache.org/upgrading.html#upgrade0.96 > > >> It does in-place upgrade of a 94 installation to 96. > > >> > > >> In case your 96 is fresh, you could dump/copy all your 94 data under > > root > > >> dir, and run the upgrade script. > > >> No, 96 doesn't convert each table automatically, one need to use the > > >> upgrade script. > > >> > > >> > > >> Himanshu > > >> > > >> > > >> On Sun, Nov 10, 2013 at 11:34 AM, Jean-Marc Spaggiari < > > >> jean-marc@spaggiari.org> wrote: > > >> > > >> > Hi, > > >> > > > >> > I have a 0.94 (hadoop 1.0.3) cluster that I want to migrate to a > 0.96 > > >> > (hadoop 2.2.0) cluster. However, there is no network connection > > between > > >> the > > >> > 2 clusters... What's the best way to do that? > > >> > > > >> > I tried with a single table first. Did an extract from 0.94 to the > > local > > >> > disk using hadoop get of all the files into /hbase/tablename and > tried > > >> to > > >> > re-import on the 0.96 side. I was able to see the table name, but > not > > >> the > > >> > content. I guess because of namespace and others, it's not doable? > > >> > > > >> > Another option is to export in CVS format, then transfer. the files, > > and > > >> > re-import on the 0.96 side. But I would have liked to keep the > regions > > >> > splits, etc. > > >> > > > >> > So the only working option I see for now is the CVS. Any other one? > > >> > > > >> > Next, if I'm able to get a network between the 2 clusters, then > > >> copytable > > >> > should be the best option? Or an I "simply" dist-cp with entire > /hbase > > >> > folder? I guess this last option is not reall correct since I will > > have > > >> a > > >> > 0.94 format in the 0.96 cluster. Or will the 0.96 cluster > > automatically > > >> > convert each table with is in the old format? > > >> > > > >> > Thanks, > > >> > > > >> > JM > > >> > > > >> > > > > > > > > > --047d7b672a9674241c04eaea0e32--