path has stupid bug with double lock...
Index: core/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
===
--- core/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
(wersja 942215)
+++ core/src/main/java/org
I figured out what is taking so long, test data was 1 row with 10
columns and 1 with 100
when i try to increament column this huge row data didnt land in
MemStore and times was(test in python after warmup):
before path:
#get one column from big row
1 0:00:00.919464
#get one column from sm
jstack is a handy tool:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html
On Tue, May 11, 2010 at 9:50 AM, Sebastian Bauer wrote:
> Ram is not a problem, second region server using about 550mB and first
> about 300mB problem is with CPU, when i making queries to both column
> famiel
Ram is not a problem, second region server using about 550mB and first
about 300mB problem is with CPU, when i making queries to both column
famielies second region server is using ablut 40% - 80% first about 10%,
after turning off queries to AdvToUsers(this big) CPU on both servers
are 2-7%.
You could try thread-dumping the regionserver to try and figure where
its hung up. Counters are usually fast so maybe its something to do
w/ 8k of them in the one row. What kinda numbers are you seeing? How
much RAM you throwing at the problem?
Yours,
St.Ack
On Tue, May 11, 2010 at 8:51 AM,
