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 vrodionov@carrieriq.com
 designates 204.235.122.16 as permitted sender)
From: Vladimir Rodionov <vrodionov@carrieriq.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Date: Thu, 5 Jan 2012 15:30:31 -0800
Subject: OfflineMetaRepair?
Thread-Topic: OfflineMetaRepair?
Thread-Index: AQHMzAJrz9K04mBnMUCcUwuMk0IBtw==
Message-ID: 
 <DC5EBE7F3610EB4CA5C7E92D76873E151714EB3D86@exchange2007.carrieriq.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

0.90.5

I am trying to repair .META. table using this tool

1.  HBase cluster was shutdown

Then I ran:

2. [name01 bin]$ hbase org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair =
-base hdfs://us01-ciqps1-name01.carrieriq.com:9000/hbase -details


This is waht I got:

12/01/05 23:23:15 INFO util.HBaseFsck: Loading HBase regioninfo from HDFS..=
.
12/01/05 23:23:30 ERROR util.HBaseFsck: Bailed out due to:
java.lang.IllegalArgumentException: Wrong FS: hdfs://us01-ciqps1-name01.car=
rieriq.com:9000/hbase/M2M-INTEGRATION-MM_TION-1325190318714/0003d2ede276687=
37e192d8430dbe5d0/.regioninfo, expected: file:///
        at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:352)
        at org.apache.hadoop.fs.RawLocalFileSystem.pathToFile(RawLocalFileS=
ystem.java:47)
        at org.apache.hadoop.fs.RawLocalFileSystem.getFileStatus(RawLocalFi=
leSystem.java:368)
        at org.apache.hadoop.fs.FilterFileSystem.getFileStatus(FilterFileSy=
stem.java:251)
        at org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSInputChecker.<=
init>(ChecksumFileSystem.java:126)
        at org.apache.hadoop.fs.ChecksumFileSystem.open(ChecksumFileSystem.=
java:284)
        at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:398)
        at org.apache.hadoop.hbase.util.HBaseFsck.loadMetaEntry(HBaseFsck.j=
ava:256)
        at org.apache.hadoop.hbase.util.HBaseFsck.loadTableInfo(HBaseFsck.j=
ava:284)
        at org.apache.hadoop.hbase.util.HBaseFsck.rebuildMeta(HBaseFsck.jav=
a:402)
        at org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair.main(Offline=
MetaRepair.java:90)


Q: What am I doing wrong?

Best regards,
Vladimir Rodionov
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: vrodionov@carrieriq.com

________________________________________
From: Mikael Sitruk [mikael.sitruk@gmail.com]
Sent: Thursday, January 05, 2012 4:32 AM
To: dev@hbase.apache.org
Subject: Re: book in inconsistent regarding disabling - major compaction

filled HBASE-5129

regards,
Mikael.S

On Thu, Jan 5, 2012 at 1:44 PM, <yuzhihong@gmail.com> wrote:

> Thanks for spotting this.
>
> Do you mind filing a Jira ?
>
>
>
> On Jan 5, 2012, at 3:02 AM, Mikael Sitruk <mikael.sitruk@gmail.com> wrote=
:
>
> > Hi all
> >
> > It seems that the book has some inconsistencies regarding the way to
> > disable major compactions
> >
> > According to the book in chapter 2.6.1.1. HBase Default Configuration
> >
> > hbase.hregion.majorcompaction - The time (in miliseconds) between 'majo=
r'
> > compactions of all HStoreFiles in a region. Default: 1 day. *Set to 0 t=
o
> > disable automated major compactions*.
> >
> > Default: 86400000 (
> > http://hbase.apache.org/book.html#hbase_default_configurations)
> >
> > According to the book at chapter 2.8.2.8. Managed Compactions
> >
> > "A common administrative technique is to manage major compactions
> manually,
> > rather than letting HBase do it. By default,
> > HConstants.MAJOR_COMPACTION_PERIOD is one day and major compactions may
> > kick in when you least desire it - especially on a busy system. *To "tu=
rn
> > off" automatic major compactions set the value to Long.MAX_VALUE.*"
> > According to the code org.apache.hadoop.hbase.regionserver.Store.java,
> "0"
> > is the right answer.
> >
> >
> > Regards,
> > Mikael.S
>


--
Mikael.S

Confidentiality Notice:  The information contained in this message, includi=
ng any attachments hereto, may be confidential and is intended to be read o=
nly by the individual or entity to whom this message is addressed. If the r=
eader of this message is not the intended recipient or an agent or designee=
 of the intended recipient, please note that any review, use, disclosure or=
 distribution of this message or its attachments, in any form, is strictly =
prohibited.  If you have received this message in error, please immediately=
 notify the sender and/or Notifications@carrieriq.com and delete or destroy=
 any copy of this message and its attachments.