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 # user >> Reg:delete performance on HBase table


Copy link to this message
-
Re: Reg:delete performance on HBase table
On Wed, Dec 5, 2012 at 7:46 AM, Doug Meil <[EMAIL PROTECTED]>wrote:

> You probably want to read this section on the RefGuide about deleting from
> HBase.
>
> http://hbase.apache.org/book.html#perf.deleting
So hold on. From the guide:

11.9.2. Delete RPC Behavior
>

> Be aware that htable.delete(Delete) doesn't use the writeBuffer. It will
> execute an RegionServer RPC with each invocation. For a large number of
> deletes, consider htable.delete(List).
>

> See
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HTable.html#delete%28org.apache.hadoop.hbase.client.Delete%29
So Deletes are like Puts except they're not executed the same why. Indeed,
HTable.put() is implemented using the write buffer while HTable.delete()
makes a MutateRequest directly. What is the reason for this? Why is the
semantic of Delete subtly different from Put?

For that matter, why not buffer all mutation operations?
HTable.checkAndPut(), checkAndDelete() both make direct MutateRequest calls
as well.

Thanks,
-n
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