We are thinking about simulator issue. Our clusters much less - 4 by 100 RS
however we need process data continuously too. So I created two clusters in
AWS and tried enable replication between HBase 1.4.13 and 2.2.5. But have
got error "table exists but descriptors are not the same" (I will put
Agree. It solves the problem in terms of randomizing distribution, but does
not increase cardinality.
On Tue, May 18, 2021 at 6:29 PM Bryan Beaudreault
wrote:
> Hi Mallikarjun, thanks for the response.
>
> I agree that it is hard to fully mitigate a bad rowkey design. We do make
> pretty heavy
We are not paying for CDH -- our older version of CDH (5.16.2) was
pre-licensing. We've never used CM. We are planning to migrate off of CDH
onto apache, and have 10+ years of experience working with HBase internals
and operating HBase at scale. I'm curious if anyone has knowledge of any
If you are paying for CDH then just upgrade via cloudera manager. If you are
not paying for it then I think you will find it a huge problem.
Upgade may have to be done using a version 6 then a newer version to get to a
suitable Hbase/Hadoop version.
We are currently on CDH6.3.2 but the Hbase
We are running about 40 HBase clusters, with over 5000 regionservers total.
These are all running cdh5.16.2. We also have thousands of clients (from
APIs to kafka workers to hadoop jobs, etc) hitting these various clusters,
also running cdh5.16.2.
We are starting to plan an upgrade to hbase 2.x
All Phoenix devs/users (in addition to SFDC and Cloudera), please feel free
to provide your opinions on whether you are using 4.x versions and what
your future plans look like, what category of issues you are facing (if
any) from stable features provided by Apache Phoenix 4.x.
Your opinions are
I agree, EOL schedule is more important as we prepare to move to Phoenix 5.
We are going to initiate official discussion for the upcoming big features
e.g dual cluster support and where it fits well (as discussed over slack by
Daniel).
As far as 4.16 is concerned, IMHO we should prefer retiring
Hi!
I am looking forward to less backports, and I want to use Java 8 features
freely as much as the next developer.
However, I'm going to play the devil's advocate here, and spell out what
Ankit hinted at:
We know that SFDC is the main contributor, and probably also the single
largest user of
