I have four HBase clusters (A, B, C, D) with replication between them. I've
configured each cluster to replicate to all other clusters in an attempt to
have a hot-hot, eventually-consistent-across-all-clusters setup. One nice
property of this configuration is that any individual cluster can
Hi,
I have a row key like this:
:
There are millions of records per id throughout the day.
When querying for id=xyz, I want one row (either the first or the last
depending) for every 5 minute time bucket in a specific time range.
I can do this efficiently with a single scan and custom filter
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
Sure: https://issues.apache.org/jira/browse/HBASE-24506
On Thu, Jun 4, 2020 at 6:29 PM 张铎(Duo Zhang) wrote:
> Please open an issue?
>
> Whitney Jackson 于2020年6月5日周五 上午5:51写道：
>
> > I ran into an issue where one instance in a cluster of application
> servers
> &
I ran into an issue where one instance in a cluster of application servers
backed by HBase stopped processing requests. Looking at a thread dump, it
seems HBase client threads are deadlocked:
https://pastebin.com/raw/B3FJL1Ag
The deadlock seemed to happen at the same time that a region server
cleared up.
>
> On Mon, Jan 27, 2020 at 11:19 AM Whitney Jackson
> wrote:
> >
> > Thanks for the reply! Very helpful.
> >
> > > One more thing I'd ask is that you remember that we're all volunteers
> > here.
> >
> > Absolutely. Appreciate the e
ose who can corral Jira issues, do
> testing, and stage release candidates are very welcome and desired to
> help make our releases happen on a regular cadence. If you have the
> time/resources to help our, let us know on the dev list.
>
> - Josh
>
> On 1/27/20 11:04 AM, Whitney Ja
Hi,
I've been running 1.4.12 with replication and experiencing the "random
region server aborts" as described here:
https://issues.apache.org/jira/browse/HBASE-23169
The underlying problem and fix (woohoo!) seems to be here:
https://issues.apache.org/jira/browse/HBASE-23205
I do see there is
