How to reduce the Store File Index?Can you give me the conf filename and
parameter I need to set I am in real need. Also tell me the way to increase
hfile block size?
See 6.3.2 under http://hbase.apache.org/book.html#rowkey.design
Cheers
On Wed, Jul 24, 2013 at 12:19 AM, ARNAB MAJI bobbybi...@gmail.com wrote:
How to reduce the Store File Index?Can you give me the conf filename and
parameter I need to set I am in real need. Also tell me the way to increase
See also http://hbase.apache.org/book.html#schema.cf.blocksize
Cheers
On Wed, Jul 24, 2013 at 6:19 AM, Ted Yu yuzhih...@gmail.com wrote:
See 6.3.2 under http://hbase.apache.org/book.html#rowkey.design
Cheers
On Wed, Jul 24, 2013 at 12:19 AM, ARNAB MAJI bobbybi...@gmail.com wrote:
How to
Sorry, I missed the fact that you guys were talking about the oome thing
(the exceptions were of sockettimeout)
Can you give the log snippet where it oome'd? I want to explore this use
case :)
You have about 200 regions per server, and each region configured to 500MB
makes it 100GB data per
Thank you very much for your post , It very similar what is happening in our
environment.
Before we are going to increase HeapSize we want to make some tuning for
hbase memstore and related components.
1) Currently our configuration parameters related to memstore are
default.
--
On Aug 25, 2011, at 1:55 AM, Oleg Ruchovets wrote:
Thank you very much for your post , It very similar what is happening in our
environment.
Before we are going to increase HeapSize we want to make some tuning for
hbase memstore and related components.
We run with 12-15GB of heap, 4
Thanks for your feedback.
The point is that once we restart hbase memory footprint is far below 4 GB.
The system runs well for couple of days and then the heap reaches 4GB which
causes the region to crash.
This may indicate on memory leak since once we restart hbase the problem is
solved (or
We had a similar OOME problem and and we solved it by allocating more heap
space. The underlying cause for us was as the table grew, the StoreFileIndex
grew taking up a larger and larger chunk of heap.
What caused this to be a problem is that Memstore grows rapidly during inserts
and its
Have you looked at the logs of the region servers? That is a good first place
to look. How many regions are in your system? If you are using MSLAB, it
reserves 2MB/region as a buffer -- that can add up when you have lots of
regions.
Given so little information all my guesses are going to be
Thank you for detailed response,
On Tue, Aug 23, 2011 at 7:49 PM, Buttler, David buttl...@llnl.gov wrote:
Have you looked at the logs of the region servers? That is a good first
place to look.
How many regions are in your system?
Region Servers
Address Start Code Load
hadoop01
Are you doing some intensive tasks at the RegionServer side (which takes
more than default time out of, 60 sec - iirc)?
One can get these exception when client side socket connection is closed
(probably a time out from client side).
As per the exception, when RegionServer tried to send the result
I won't say you're crazy but .5 GB per mapper?
I would say tune conservatively like you are suggesting 1GB for OS, but also
I'd suggest tuning to 80% utilization instead of 100% utilization.
From: buttl...@llnl.gov
To: user@hbase.apache.org
Date: Tue, 23 Aug 2011 16:35:22 -0700
Subject:
12 matches
Mail list logo
