Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> flushing + compactions after config change


+
Viral Bajaria 2013-06-27, 07:40
+
Anoop John 2013-06-27, 07:51
+
Viral Bajaria 2013-06-27, 08:18
+
谢良 2013-06-27, 08:21
+
Viral Bajaria 2013-06-27, 08:29
Copy link to this message
-
Re: 答复: flushing + compactions after config change
The config "hbase.regionserver.maxlogs" specifies what is the max #logs and
defaults to 32.  But remember if there are so many log files to replay then
the MTTR will become more (RS down case )

-Anoop-
On Thu, Jun 27, 2013 at 1:59 PM, Viral Bajaria <[EMAIL PROTECTED]>wrote:

> Thanks Liang!
>
> Found the logs. I had gone overboard with my grep's and missed the "Too
> many hlogs" line for the regions that I was trying to debug.
>
> A few sample log lines:
>
> 2013-06-27 07:42:49,602 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> Too many hlogs: logs=33, maxlogs=32; forcing flush of 2 regions(s):
> 0e940167482d42f1999b29a023c7c18a, 3f486a879418257f053aa75ba5b69b14
> 2013-06-27 08:10:29,996 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> Too many hlogs: logs=33, maxlogs=32; forcing flush of 1 regions(s):
> 0e940167482d42f1999b29a023c7c18a
> 2013-06-27 08:17:44,719 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> Too many hlogs: logs=33, maxlogs=32; forcing flush of 2 regions(s):
> 0e940167482d42f1999b29a023c7c18a, e380fd8a7174d34feb903baa97564e08
> 2013-06-27 08:23:45,357 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> Too many hlogs: logs=33, maxlogs=32; forcing flush of 3 regions(s):
> 0e940167482d42f1999b29a023c7c18a, 3f486a879418257f053aa75ba5b69b14,
> e380fd8a7174d34feb903baa97564e08
>
> Any pointers on what's the best practice for avoiding this scenario ?
>
> Thanks,
> Viral
>
> On Thu, Jun 27, 2013 at 1:21 AM, 谢良 <[EMAIL PROTECTED]> wrote:
>
> > 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
> >
>
+
Azuryy Yu 2013-06-27, 09:22
+
Viral Bajaria 2013-06-27, 09:47
+
Azuryy Yu 2013-06-27, 09:48
+
Viral Bajaria 2013-06-27, 10:08
+
谢良 2013-06-27, 10:36
+
Azuryy Yu 2013-06-27, 14:53
+
Viral Bajaria 2013-06-27, 21:06
+
Jean-Daniel Cryans 2013-06-27, 21:40
+
Viral Bajaria 2013-06-27, 23:27
+
Jean-Daniel Cryans 2013-06-28, 16:31
+
Viral Bajaria 2013-06-28, 21:39
+
Jean-Daniel Cryans 2013-06-28, 23:53
+
Himanshu Vashishtha 2013-07-01, 06:08
+
Azuryy Yu 2013-06-28, 01:09
+
Viral Bajaria 2013-06-28, 01:22
+
Anoop John 2013-06-28, 12:08
+
谢良 2013-06-27, 08:53