On Wed, Jul 11, 2018 at 7:19 PM, Manjeet Singh
<[EMAIL PROTECTED]> wrote:
Once the HBase replication system is active and there's a peer (even a
disabled peer) it starts retaining WALs until they have been
successfully acknowledged by all peer clusters. Since the Lily Indexer
for HBase makes use of the replication system to get an stream of
edits, the WALs will stick around until the indexer has said it saw
the edits in them.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB