On Mon, Jun 29, 2020 at 11:07 AM Govindhan S
wrote:
> I got this figured out and solved.
> Issue with the AMSà Advanced AMS-hbase-env-template à optional_cp (given
> below)
> Had extra : present with wrong Jar file, hence the issue. Correcting the
> same cleared me.
> Thanks everyone.
> ~
I got this figured out and solved.
Issue with the AMSà Advanced AMS-hbase-env-template à optional_cp (given below)
Had extra : present with wrong Jar file, hence the issue. Correcting the same
cleared me.
Thanks everyone.
~ Govins
On Friday, 26 June, 2020, 10:00:56 pm IST, Govindhan S
Can you figure which key it is?
This seems common enough issue grepping the web. There is even an old
complaint in hbase JIRA that was resolved long ago. It is likely fixed in
later versions. You are running an old version. Can you upgrade?
Thanks,
S
On Fri, Jun 26, 2020 at 10:14 AM Govindhan S
>
> Nice. I didn't know about this. I see the tool wants you to specify a
> desired number of regions. In my particular case I don't have a view on the
> number of regions I want. I just know that all the post compaction 0 sized
> regions should go. Can I still make use of this tool?
For optimal
On Mon, Jun 29, 2020 at 7:13 AM Whitney Jackson wrote:
> > The trouble is we ship defaults for all of the `*min*` configs, and right
> now there's no way to "unset" them, disable the functionality.
>
> Why is that the case? Can I not just set
> hbase.normalizer.merge.min_region_size.mb to 0? Do
I was just facing the many-zero-sized-regions issue last week and pondering
how best to approach it. So ++ for this work!
> The trouble is we ship defaults for all of the `*min*` configs, and right
now there's no way to "unset" them, disable the functionality.
Why is that the case? Can I not
Hi, Apache enthusiast!
(You’re receiving this because you’re subscribed to one or more dev or
user mailing lists for an Apache Software Foundation project.)
The ApacheCon Planners and the Apache Software Foundation are pleased to
announce that ApacheCon @Home will be held online, September
>
> The trouble is we ship defaults for all of the `*min*` configs, and right
> now there's no way to "unset" them, disable the functionality. Which means
> there still isn't a way to support the empty regions use-case without
> awkward special-case checks.
>
HBASE-23562 added a RegionsMerger