To be 100% honest, I really like the admin throwing an error! It triggers
the attention.
I did a distscp from CDH 5.12 to a brand new HBase 2.0 cluster. I'm not
100% sure if I have the same issue on the source side.
Just ran HBCK on the source and I have the same issue. So at least it's
consistent. Just HBaseAdmin that is triggering this new message. I like it
;)
JMS
2018-02-23 15:11 GMT-05:00 Stack <st...@duboce.net>:
> On Fri, Feb 23, 2018 at 11:04 AM, Jean-Marc Spaggiari <
> jean-m...@spaggiari.org> wrote:
>
> > Hi guys,
> >
> > In HBase 2.0.0-beta-1, getting this:
> >
> > 2018-02-23 14:01:55,499 WARN [main] client.HBaseAdmin
> > (HBaseAdmin.java:visit(1948)) - No serialized HRegionInfo in
> > keyvalues={page_proposed,,1384198043055.c15b13946fa4318a0a956e067d59eb
> > d4./info:server/1384198854149/Put/vlen=11/seqid=0,
> > page_proposed,,1384198043055.c15b13946fa4318a0a956e067d59eb
> > d4./info:serverstartcode/1384198854149/Put/vlen=8/seqid=0}
> >
> >
> > I'm not getting that on other versions. And I'm not sure what it means...
> >
> > Any idea?
> >
> >
> The Admin client is getting detail from hbase:meta. It found a row where
> there was no serialized regioninfo and is WARNing you of this. This should
> never happen. It is dumping out all it did find in the meta table.
>
> Why no regioninfo in hbase:meta? This a fresh hbase2 or are you starting an
> hbase2 over an old hbase1 dataset? If latter, could it have been null
> before the update?
>
> Thanks,
> S
>
>
>
> > Thanks,
> >
> > JMS
> >
>
