Below is an interesting finding on our hbase client by Jonathan Payne.
He posted the asynchbase list. I'm forwarding here (with his
permission).
St.Ack
-- Forwarded message --
From: Jonathan Payne jpa...@flipboard.com
Date: Fri, Oct 21, 2011 at 6:30 PM
Subject: standard
Another reason of commenting in JIRA directly, for reviewing large projects,
is that the reviewer may not have ample time (3 hours or more) to write
thorough review using review board.
Before review board integration redundancy is minimized, it seems impolite
to sprinkle JIRA with multiple reviews
See https://builds.apache.org/job/HBase-TRUNK/2358/
Hi All HBASE-4462 first version of patch is up for review. Pls provide your
comments. RegardsRam
See https://builds.apache.org/job/HBase-TRUNK/2357/
--
[...truncated 1705 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.913 sec
Running org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster
Tests run: 4, Failures:
On Sat, Oct 22, 2011 at 1:17 AM, Dhruba Borthakur dhr...@gmail.com wrote:
One of the current problems with hbase eating lots of cpu is the fact that
the memstore in a sortedset. Instead, we can make it a hashset so that
lookup and insertions are much faster. At the time of flushing, we can sort
Hi,
On Sat, Oct 22, 2011 at 11:33 PM, Stack st...@duboce.net wrote:
On Sat, Oct 22, 2011 at 1:17 AM, Dhruba Borthakur dhr...@gmail.com
wrote:
How would you scan in order an HashSet? Deletes across spans
(families or all older than a particular timestamp)?
On the other hand, I did have a
On Sat, Oct 22, 2011 at 2:41 PM, N Keywal nkey...@gmail.com wrote:
I would think that the bottleneck for insert is the wal part?
It would be possible to do a kind of memory list preparation during the wal
insertion, and if the wal insertion is confirmed, do the insertion in the
memory list.
