Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates
 209.85.214.41 as permitted sender)
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: 
 <CADcMMgE7L51qoP4C0U=B4iZ+Hh6EHb38kk8yqgroFKcmWUNpmw@mail.gmail.com>
References: <1341534984.68303.YahooMailNeo@web121705.mail.ne1.yahoo.com>
	<CA+ULb+uC3zLkpisy-vKqe-6oOiv8iV4+LaNOfKF7FAeBbOx9ZA@mail.gmail.com>
	<1341875234.78322.YahooMailNeo@web121704.mail.ne1.yahoo.com>
	<CALte62ybNkAXwLEuuJ5EggQ4fEDiGm9jBCB25-sEoTx-OsW3Gw@mail.gmail.com>
	<1341877583.95448.YahooMailNeo@web121706.mail.ne1.yahoo.com>
	<CALte62x_42hmP=v5YjQtD56WeQdV_g7WJqZLi66S5qaB-aTT3A@mail.gmail.com>
	<A6C8D9EA-F00C-4DF5-AC22-1170646FD6D8@gmail.com>
	<CALte62wmx5v6RUNwEHzuvZAaZKBySF=eBbQVhBU3z3M+fpq0gQ@mail.gmail.com>
	<CAKfebOMju+-j+grjU6WxDRseRpAdO-RgOf_1yrwUmpCDMEQ5zw@mail.gmail.com>
	<CADcMMgE7L51qoP4C0U=B4iZ+Hh6EHb38kk8yqgroFKcmWUNpmw@mail.gmail.com>
Date: Tue, 10 Jul 2012 09:55:47 -0700
Message-ID: 
 <CAGpTDNfOL2Lx3CvN_-yuOHTzOrCBtv-0zGK322=4DqqogVGHZw@mail.gmail.com>
Subject: Re: HBase 0.94.1
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jul 10, 2012 at 9:37 AM, Stack <stack@duboce.net> wrote:
> I'd usually update the stable pointer to the new .0 release but didn't
> this time.  It was part oversight and partly the fact that we've not
> brought 0.94 up fully at SU yet.

To follow up on that, 0.94 is only on a dev cluster at the moment and
we're about to deploy a new refresh. One issue that's really a blocker
for us is:

https://issues.apache.org/jira/browse/HBASE-6310 "-ROOT- corruption
when .META. is using the old encoding scheme"

I can't have my clusters fail to boot after some outage because .META.
isn't reachable. We're still digging.

Another issue that I haven't looked into too much yet is that the new
hbck cannot be used on an old cluster.

Right now what I'm getting is not what I usually get but it's:

ERROR: .META. is found on more than one region.
ERROR: Encountered fatal error. Exiting...
Summary:
2 inconsistencies detected.
Status: INCONSISTENT

Although:


hbase(main):001:0> scan '-ROOT-'
ROW                                           COLUMN+CELL
12/07/10 16:51:58 INFO security.UserGroupInformation: JAAS
Configuration already set up for Hadoop, not re-installing.
 .META.,,1                                    column=info:regioninfo,
timestamp=1331755381142, value={NAME => '.META.,,1', STARTKEY => '',
ENDKEY => '', ENCODED => 1028785192,}
 .META.,,1                                    column=info:server,
timestamp=1341618049327, value=sfor3s40:10304
 .META.,,1
column=info:serverstartcode, timestamp=1341618049327,
value=1341515423853
 .META.,,1                                    column=info:v,
timestamp=1331755419291, value=\x00\x00
1 row(s) in 0.5370 seconds


So I guess it's something new we need to debug...