Yah, we use Phoenix in a lot of tables so it wont be possible to remove
that. We are already migrating to a newer cluster but we need to operate on
this cluster for a while during migration.
Although we are running HDP but IMO, this seems to be something related to
vanilla(Apache) Hadoop/HBase. So,
Do you use Phoenix functionality ?
If not, you can try disabling the Phoenix side altogether (removing Phoenix
coprocessors).
2.3.4 is really old - please upgrade to 2.6.3
You should consider asking on the vendor's community forum.
Cheers
On Thu, Feb 8, 2018 at 3:06 PM, anil gupta wrote:
> H
Hi Folks,
We are running a 60 Node MapReduce/HBase HDP cluster. HBase 1.1.2 , HDP:
2.3.4.0-3485. Phoenix is enabled on this cluster.
Each slave has ~120gb ram. RS has 20 Gb heap, 12 disk of 2Tb each and 24
cores. This cluster has been running OK for last 2 years but recently with
few disk failure
First the version details:
Running HBASE/Yarn/HDFS using Cloudera manager 5.12.1.
Hbase: Version 1.2.0-cdh5.8.0
HDFS/YARN: Hadoop 2.6.0-cdh5.8.0
Hbck and hdfs fsck return healthy
15 nodes, sized down recently from 30 (other service requirements reduced.
Solr, etc)
The simplest example of the i
Great to know. There seems to be quite some adoption of 1.3 to support
moving our stable pointer.
Mind share the number of votes boss? Please forgive my ignorance if it's
shown in the inline image since I cannot read it (picture failed to open)
Best Regards,
Yu
On 8 February 2018 at 09:07, Andre
