Thanks for the help.
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/HBase-prioritizing-writes-over-reads-tp4042838p4043876.html
Sent from the HBase User mailing list archive at Nabble.com.
I've following settings:
hbase.master.handler.count = 25 (default value in CDH4.2)
hbase.regionserver.handler.count = 20 (default 10)
--
View this message in context:
http://apache-hbase.679495.n3.nabble.com/HBase-Performance-issue-tp4042836p4042840.html
Sent from the HBase User mailing list
Is it possible to prioritize writes over reads in HBase? I'm facing some I/O
read related issues that influence my write clients and cluster in general
(constantly growing store files on some RS). Due to the fact that I cannot
let myself to loose/skip incoming data, I would like to guarantee that i
The problem is that when I'm putting my data (multithreaded client, ~30MB/s
traffic outgoing) into the cluster the load is equally spread over all
RegionServer with 3.5% average CPU wait time (average CPU user: 51%). When
I've added similar, mutlithreaded client that Scans for, let say, 100 last
sa
Thanks, but I've already read that article and I was trying to set up
settings accordingly. But any type of help could be useful. Here are logs
(compressed with tar gzip): hbase_logs.tar.gz
<http://apache-hbase.679495.n3.nabble.com/file/n4037960/hbase_logs.tar.gz>
Kevin O'del
at can affect your flush size?
Initial split is 37 regions on 6 RegionServers, but at the moment there are
71 regions.
Kevin O'dell wrote
> Kzurek,
>
> Just because you turn off time based major compactions, it does not mean
> that you have turned major compaction off. Compaction ca
I'm facing some issues regarding to major compaction. I've disabled major
compaction and it is not triggered manually, but when I'm loading data to
selected region, I saw that major compaction queue is growing and it is
being triggered ('Large Compaction' in logs) quite often (mainly due to
cacheFl
0~i\x91\x00\x00\x00\x0D,1359115210217.3b710693d6314c2a987b07dd82451158.
'IPC Server handler 10 on 60020'
2013-02-01 15:44:55,087 INFO org.apache.hadoop.hbase.regionserver.HRegion:
Finished memstore flush of ~1.5g/1624094576, currentsize=0.0/0 for region
test,\x00\x00\x00\x00~i\x91\x0
Hi,
I'm having following issues with triggering manually major compaction on
selected regions via HBaseAdmin:
1. When I'm triggering major compaction on first region, which does not
contains key, it's running normally - I see message in logs ([..]Large
Compaction requested ... Because: User-tri
