In our cluster, there're thousands of region and each region has 5-8 store
files, so the connection number is very terrible.
And if we close the store file after scanning , the connection number may
bring down some region servers. (In my cluster , my region server went down
caused by socket OOM,
Let me try . Thanks very much for your help.
:D
Thanks Best regards
LiuJinglong
在 2010年7月30日 下午3:35,Angus He angu...@gmail.com写道:
Close the scannner will not close the store file.
Probably you could increase the memstore size and region file size.
And hbase.hstore.compactionThreshold and
hi!
seems stargate saves state of previous requests. For example if I try to
put row and supply wrong column name. NoSuchColumnFamilyException
exception will be thrown for all other requests (even with corrected
column name). Exception is disappear only when I restart stargate
server. Is
If your customers data fits in one region, then no. For example, if
you have 1k tables then you would have 1k regions, those will be
distributed to the region servers but if any of them becomes a
hotspot, too bad. BTW a region is the basic unit of load distribution
in HBase.
I see. Usually
seems stargate saves state of previous requests.
If so that's unintentional, and not the way the Jersey/JAX-RS framework works
according to my understanding.
if I try to put row and supply wrong column name.
NoSuchColumnFamilyException exception will be thrown for all
other requests (even
I see. Usually a whole customer fits within a region. Actually, the
number of customers that doesn't fit in a single region are only two or three.
But then another question comes up. Even if a put all the data in a single
table, given that the keys are written in order, and given that several
GC paused of 5 minutes seems to be my bane. I disable swapping
sysctl -A |grep swap
vm.swappiness = 0
so I assume Java heap is not swapped out. How do one check whether swapping
is on for a particular Java process.
swappiness is something else, it's good to set it at 0 when you have
enough RAM to fit everything but it will still swap when you run out
if it and it will be a big hit.
I would advise monitoring the cluster, or at least very least look at
the output of the top command while the job is running.
HBase 0.20.6 is available for download:
http://hadoop.apache.org/hbase/releases.html
The Release Notes are available here: http://su.pr/2itvaW
We recommend that all users, particularly those running 0.20.4, upgrade.
Thanks to all who contributed to this release.
Yours,
The HBasistas
406 Not Acceptable is what I get with -i option. Thanks for pointing me to
it.
While playing around, I found that if my url has row_id followed by column name
then I get the output I expect !
curl -H Accept: application/octet-stream
http://localhost:8000/table_name/row_id/column_name
I am pretty sure that is the case but will double check.
I found another case where RS died without an apparent stop-the-world GC.
RS grv-hadoopc05
*** rs.log ***
2010-07-30 10:43:36,028 INFO org.apache.hadoop.hbase.regionserver.HLog: Roll
11 matches
Mail list logo