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 Threaded View
HBase >> mail # dev >> reason to do major compaction after split


Copy link to this message
-
Re: reason to do major compaction after split
Hmm... should we have hardlinks (or use HDFS hardlinks if any?) to solve
this problem.
HalfHFile could be HFileWithRange :)

On Thu, Mar 7, 2013 at 2:13 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Thu, Mar 7, 2013 at 1:14 PM, Enis Söztutar <[EMAIL PROTECTED]>
> wrote:
>
> > We do not have to created references to references. We can find the
> > original file, and directly create a ref at the grand daughters. The
> messy
> > part, is in the cleanup for parent region, where we have to recursively
> > search for all successors to decide whether we can delete this region,
> and
> > delete the hfile.
> >
>
> Yes.  That is a few trips to the NN listing directory contents and then
> some edits/reading of .META.  We would have to introduce a QuarterHFile to
> go with our HalfHFile (or rename HalfHFile as PieceO'HFile).
>
>
> St.Ack
>
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