Hi,
We are running a medium sized HBase cluster (12 data nodes) with around 200 TB
of data (w/o replication). When a node fails, the time to (fully) recover is in
the order of 30 minutes. We’re looking for ways to reduce this. Almost two
years ago, we already ‘discovered’ the hbase.wal.split.to
Hello everyone,
We've discussing an idea internally at Cloudera about implementing the
open source version of [1] Amazon's EMR Read Replica Clusters on Amazon
S3. A feature which would let us run HBase in read-only mode and having
another cluster running on the same storage location, will be
poten