Yes, bow main issue in "hole".
Could you give me example how I can fetch or scan section of the table?
Thanks.
On Mon, Sep 10, 2018 at 1:53 PM Stack <st...@duboce.net> wrote:
> On Mon, Sep 10, 2018 at 1:32 PM Oleg Galitskiy <galitskiy.o...@gmail.com>
> wrote:
>
> > Hello,
> >
> > Faced with inconsistent issues on HBase 2.0.1:
> > --
> >
> > ERROR: Region \{ meta => null, hdfs =>
> >
> >
> hdfs://master:50001/hbase/data/default/some_table/0646d0bee757d0fb0de1529475b5426f,
> > deployed =>
> >
> hbase-region,16020,1536493017073;some_table,,1534195327532.0646d0bee757d0fb0de1529475b5426f.,
> > replicaId => 0 } not in META, but deployed on
> > hbase-region,16020,1536493017073...
> > ERROR: hbase:namespace has no state in meta
> > ERROR: table1 has no state in meta
> > ERROR: table2 has no state in meta
> > 2018-09-09 21:40:04,155 INFO [main] util.HBaseFsck: Handling overlap
> > merges in parallel. set hbasefsck.overlap.merge.parallel to false to
> > run serially.
> > ERROR: There is a hole in the region chain between and . You need to
> > create a new .regioninfo and region dir in hdfs to plug the hole.
> > ERROR: Found inconsistency in table test3
> >
> > --
> >
> > BUT in 2.0.x HBAse version options *-repair, -fix, -fixHdfsHoles, etc*
> was
> > deprecated.
> > How I can fix it without these options?
> >
> > The main question now - is how to fix "hole":
> > --
> > ERROR: There is a hole in the region chain between
> > \x01yyyymmdd=20180813|ad= 0|source= rubicon|site=
> >
> > demorgen.be|placement= 1892806 and \x01yyyymmdd=20180817|ad=
> > 0|source= index|site=
> > dailynews.co.th|placement=
> > 1898. You need to create a new .regioninfo and region dir in hdfs to
> plug
> > the hole.
> > --
> >
> >
> Yeah, hbck1 can't repair an hbase2 cluster.
>
> And for sure, you have a 'hole'? What happens if you fetch or scan that
> section of the table?
>
> Please update to 2.0.2 also.
>
> S
>
>
>
>
> > Thanks.
> >
>
