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 5F9D3D0A8 for ; Tue, 9 Oct 2012 20:30:51 +0000 (UTC) Received: (qmail 86665 invoked by uid 500); 9 Oct 2012 20:30:49 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 86463 invoked by uid 500); 9 Oct 2012 20:30:49 -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 Delivered-To: moderator for user@hbase.apache.org Received: (qmail 84628 invoked by uid 99); 9 Oct 2012 18:51:49 -0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kevin@ie.suberic.net designates 209.85.214.169 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=BxFDfLFJ5gj3S2kMuf7abcRG20tIbmrKg3jSB4dz8SE=; b=c9Vf1rjcout0C4UASv9yO6d977uQZtebRhMSnoaf5ubwijEnJPBpJf1PvwpZCKoAnM LotlFUIiKGs0YZQHQhGDXupto2A3MmALfcQHPvaU6iYvTP+HSl+C2Zt7wz3RYBQXM+U4 ziCHgcl/sx1/gg2R5NeR7N8ICXbpUM9GwZn0y4yEcH0+Zzy7/VfZPelpuzuUfbG8NDfh 5umnja94YmeQCJOYifFtkN94QaY2Z+hgE7qkoqDxvx0hMbwT2jn1slt+KU16mJO4StS5 eityjRO0ZN10zcq4qaPPlGsNhMwAJrCwpnh31H0vKHOYLvP2SlZrTOnfzagXaJc0xtL8 JM4w== MIME-Version: 1.0 Date: Tue, 9 Oct 2012 19:51:17 +0100 Message-ID: Subject: HBase 0.92.1 questions... From: Kevin Lyda To: "HBase User's List" Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQn9akxrJnDCro0pMqXXd9oCtgHKNByMhK+Jhqw0DUpRFXdMeURqI7DYIBb67DBmyEP5CCcs HBase n00b here, sorry for the level of the questions I'm about to spit out. I have gone hunting for answers for the past few days. I have an HBase that was recently upgraded from 0.20.6 to 0.92.1. This was done just as I was starting so I'm not clear on the state of the HBase prior to the upgrade. Currently an hdck of it yields loads of "[blah] is listed in META on region server [fluffy] but is multiply assigned to region servers [froofy], [moofy], [floyd]". By loads I mean tens of thousands. I gave a -fix option to hdck, but the errors remain. In reading the docs I learned that hdck in 0.92.2 has some additional -fix* options, and -fixAssignments and -fixMeta seem like they might fix this. I also got the impression that one could run the 0.92.2 version of hdck on a 0.92.1 HBase - possibly needing to restart the master server after it completes (or does the master server need to be stopped, hdck run and then the master server brought up after completion?). It also appears that a rolling upgrade to 0.92.2 is possible - but it says the hdck should be clean. Lastly I note that there are two release tarballs for each version: hbase-VERSION.tar.gz and hbase-VERSION-security.tar.gz. However I can't seem to find any references to what this means. Is the -security tarball just a version with security patches added, or does it mean something else? Thanks for any help. Kevin -- Kevin Lyda Dublin, Ireland US Citizen overseas? We can vote. Register now: http://www.votefromabroad.org/