Thank you for all the helps Stack! It must have cost lots of your time
downloading the videos then uploading to youtube, uploading slides onto
slideshare, and put up all together into the blog!
The success of the conference is attributed to all PC members and supports
from hbase community rather t
If it was related to maxClientCnxns, you would see sessions being
torn-down and recreated in HBase on that node, as well as a clear
message in the ZK server log that it's denying requests because the
number of outstanding connections from that host exceeds the limit.
ConnectionLoss is a transi
Hi Team,
Need help below data modelling in HBase.
We have nested structure trying to model in HBASE.
The problem I am facing is HBase support one level nested entity and my
data has multiple inner level nested entity. Need guidance how to model in
HBASE
We have below data in hive table and st
I have played around with ReadReplicas a fair bit and that might be a
good enough stopgap should something go wrong. Ideally we wouldn't loose
the primary cluster but that may not be reasonable with our given
configuration.
Thanks,
Austin
On 08/31/2018 03:50 PM, Zach York wrote:
Hey Austin,
Hey Austin,
It sounds like you are asking about read availability in the case where a
primary cluster becomes unhealthy?
In that case, you should look at the HBase on S3 Read Replica clusters
feature[1][2]. This allows for High availability reads if the primary
cluster becomes unhealthy.
Let me
Hello all,
Our production application has recently experienced a very high spike in the
following exception along with very large read times to our hbase cluster.
“org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /
On Fri, Aug 31, 2018 at 10:22 AM Chetan Khatri
wrote:
> Thank you Stack for everything.
>
>
Thanks Chetan but our mighty Yu Li did all the work!
S
> On Fri, Aug 31, 2018 at 8:18 PM Stack wrote:
>
> > I blew the cobwebs off our blog and put up a short note on the conference
> > by Yu Li and my
Thank you Stack for everything.
On Fri, Aug 31, 2018 at 8:18 PM Stack wrote:
> I blew the cobwebs off our blog and put up a short note on the conference
> by Yu Li and myself. See here: https://blogs.apache.org/hbase/
>
> S
>
> On Wed, Aug 22, 2018 at 3:03 AM Yu Li wrote:
>
> > Hi all,
> >
> >
Hey JMS,
No, that's not my understanding. I'm not sure how the Normalizer would
change the size of the Regions but keep the number of Regions the same :)
IIRC, the Normalizer works by looking at adjacent Regions, merging them
together when their size is under the given threshold. The caveat i
I blew the cobwebs off our blog and put up a short note on the conference
by Yu Li and myself. See here: https://blogs.apache.org/hbase/
S
On Wed, Aug 22, 2018 at 3:03 AM Yu Li wrote:
> Hi all,
>
> HBaseConAsia2018 is successfully held on Aug. 17th in Beijing, China and
> please following below
If I'm not mistaken the Normalizer will keep the same number of regions,
but will uniform the size, right? So if the goal is to reduce the number of
region, the Normalizer might not help?
JMS
Le ven. 31 août 2018 à 09:16, Josh Elser a écrit :
> There's the Region Normalizer which I'd presume wo
I'd like to remind you again that we're all volunteers and we're helping
you because we choose to do so. Antagonizing those who are helping you
is a great way to stop receiving any free help.
If you do not create more than one Region, HBase will not distribute
your data on more than one Region
There's the Region Normalizer which I'd presume would be in an HBase 1.4
release
https://issues.apache.org/jira/browse/HBASE-13103
On 8/30/18 3:50 PM, Austin Heyne wrote:
I'm using HBase 1.4.4 (AWS/EMR) and I'm looking for an automated
solution because I believe there are going to be a few hun
13 matches
Mail list logo
