hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 谢良 <xieli...@xiaomi.com>
Subject 答复: flushing + compactions after config change
Date Thu, 27 Jun 2013 08:21:12 GMT
If  reached memstore global up-limit,  you'll find "Blocking updates on" in your files(see
MemStoreFlusher.reclaimMemStoreMemory);
If  it's caused by too many log files, you'll find "Too many hlogs: logs="(see HLog.cleanOldLogs)
Hope it's helpful for you:)

Best,
Liang
________________________________________
发件人: Viral Bajaria [viral.bajaria@gmail.com]
发送时间: 2013年6月27日 16:18
收件人: user@hbase.apache.org
主题: Re: flushing + compactions after config change

Thanks for the quick response Anoop.

The current memstore reserved (IIRC) would be 0.35 of total heap right ?

The RS total heap is 10231MB, used is at 5000MB. Total number of regions is
217 and there are approx 150 regions with 2 families, ~60 with 1 family and
remaining with 3 families.

How to check if the flushes are due to too many WAL files ? Does it get
logged ?

Thanks,
Viral

On Thu, Jun 27, 2013 at 12:51 AM, Anoop John <anoop.hbase@gmail.com> wrote:

> You mean there is enough memstore reserved heap in the RS, so that there
> wont be premature flushes because of global heap pressure?  What is the RS
> max mem and how many regions and CFs in each?  Can you check whether the
> flushes happening because of too many WAL files?
>
> -Anoop-
>
Mime
View raw message