Hope I'm not too late here... regarding hot spotting with sequential keys,
I'd suggest you read this Sematext blog -
http://blog.sematext.com/2012/04/09/hbasewd-avoid-regionserver-hotspotting-despite-writing-records-with-sequential-keys/
They present a nice idea there for this kind of issues.
+
http://blog.sematext.com/2012/12/24/hbasewd-and-hbasehut-handy-hbase-libraries-available-in-public-maven-repo/
if you use Maven and want to use HBaseWD.
Otis
--
HBASE Performance Monitoring - http://sematext.com/spm/index.html
On Sat, Apr 20, 2013 at 11:24 AM, Amit Sela am...@infolinks.com
I are planning to create a scheduled task list table in our hbase cluster.
Essentially we will define a table with key timestamp and then the row contents
will be all the tasks that need to be processed within that second (or whatever
time period). I am trying to do the reasonably wide rows
I assume you would select HBase 0.94.6.1 (the latest release) for this
project.
For #1, write performance would be lower if you choose to use Append (vs.
using Put).
bq. Can appends be batched by the client or do they execute immediately?
This depends on your use case. Take a look at the
Thanks for the reply. write performance would be lower - this means
better?
Also I think I used the wrong terminology regarding batching. I meant to
ask if it uses the client side write buffer. I would think not since the
append() method returns a Result. I could batch them up application
bq. write performance would be lower
The above means poorer performance.
bq. I could batch them up application side
Please do that.
bq. I guess there is no way to turn that off?
That's right.
On Mon, Apr 15, 2013 at 11:15 AM, Kireet kir...@feedly.com wrote:
Thanks for the reply. write
