Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # dev >> Account for max versions while adding to memstore


Copy link to this message
-
Account for max versions while adding to memstore
Hello,

This thread is aligned to work done in
https://issues.apache.org/jira/browse/HBASE-4241, which optimizes pruning
process before flushing MemStore.

My question is, if not already being done[1], should max versions setting
be considered while adding a KV to MemStore. In other words don't keep more
than max versions in MemStore, avoiding it to grow unnecessarily when
update to same cell are happening.
-Shrijeet
[1] HBase version 0.94.7 I did not find such logic.
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