Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 69B2518DB4 for ; Sat, 12 Mar 2016 00:38:51 +0000 (UTC) Received: (qmail 50557 invoked by uid 500); 12 Mar 2016 00:38:49 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 50488 invoked by uid 500); 12 Mar 2016 00:38:49 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 50475 invoked by uid 99); 12 Mar 2016 00:38:49 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Mar 2016 00:38:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 119F5C0DB1 for ; Sat, 12 Mar 2016 00:38:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id QiyK3hhaU1dZ for ; Sat, 12 Mar 2016 00:38:47 +0000 (UTC) Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 1B8885F640 for ; Sat, 12 Mar 2016 00:38:47 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id x1so176424581lbj.3 for ; Fri, 11 Mar 2016 16:38:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=B4Kq3Hywt3O526PohwVHRDdMVppBt0UPkwie5+/toBI=; b=NWTuRDvig7kZZnL1Q0fBHF7CgVbO3AWEIrIUET57qKUfYf4K2dV/7dpVz8yfUapM9P 9FM+Y44qlO/Psox5TNjzr7RR1gZTwlrO++5KdMluQLpkV22QhyOREdLS2d9M4ODw7mHD CBPql2rCsY/ZDF/AfjesGxEJqwmzqKPZqOs3sGjoI14r0ASZcehlrbfgSVspV/pq4/E/ TCTXl01EwV9c7Lacg8UKt0oODQdLIpqpZi7YELnmSdMGOl+ie/jkBT7gUnMbHzAr4mHy Ul2+HVx7Q972pfzp3Wn7DYhA053rzFSj8LiJ5GL4RnLN8I0XzMAqYWhVgAQjUnWLg5Uc V/5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=B4Kq3Hywt3O526PohwVHRDdMVppBt0UPkwie5+/toBI=; b=XrAi7+Q/6liA1rWs08nXUrdmIxVCxbgxqW5f06cA+p5EVCJY+DnP4dGSq2JgS2mJDH klnAFapIt+fCScUAQva3IqeF48wW+RIt3m935DhEf4JRGx9O0DfJVEnVCR9Dh7oTXlUJ gYx3v9NEx6E71dC0noWOWdc6gS9V2RblFWPi4GmhyY/sY5p/LCJoIaZNDHEWGtm8xfq3 GOL8PVJUHrzicnk7VFxdJCnwe5N22kIL1WgGl0GDGrPn4T4Y8kf/0zn49AscvbP3hL0u BnHVcVMjaFpMVdsfUcadi25X0y4LhsGfgsNZlXyJj3fEO4dNB/UOoy7tEMHSlBkjwDao bJUA== X-Gm-Message-State: AD7BkJJSDkSZvE0//r50Q5/cSpLHFX5tV+EwnRUeHSQkgHD/obBoqO5GTUnkD71+f0jGnxduyG5HdqYLooSChw== MIME-Version: 1.0 X-Received: by 10.25.212.207 with SMTP id l198mr4225294lfg.163.1457742816874; Fri, 11 Mar 2016 16:33:36 -0800 (PST) Received: by 10.112.110.167 with HTTP; Fri, 11 Mar 2016 16:33:36 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Mar 2016 16:33:36 -0800 Message-ID: Subject: Re: Hourly performance degradation on HBase cluster From: Vladimir Rodionov To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1141228cc61945052dcf32e4 --001a1141228cc61945052dcf32e4 Content-Type: text/plain; charset=UTF-8 The problem is - periodic, with 1h interval, starts at the beginning of each hour, performance degradation. I would suspect periodic memstore flusher (flushes memstores every hour, by default), but it does not explain why it happens at the beginning of each hour? May be coincidence? Grep log for "MemstoreFlusherChore". -Vlad On Fri, Mar 11, 2016 at 3:28 PM, Matteo Bertozzi wrote: > Master and RegionServer have nothing to do, to each other. > the periodic rolling you see is on the master, and it just remove a file or > two if it needs to. > > you are probably hitting GC or compactions on the Region Server which slow > you down in the insert/scan perf. > you can use a monitoring tool to visualize GC, or just add the -X option to > print the GC in the log. > also you can grep for compactions and flushes on the RS logs, to see what > is happening around that time. > > Matteo > > > On Fri, Mar 11, 2016 at 3:25 PM, Vladimir Rodionov > > wrote: > > > HBASE-13202 > > > > and Matteo Bertozzi can answer your question? > > > > -Vlad > > > > > > > > > > > > there is > > > > > > On Fri, Mar 11, 2016 at 3:02 PM, Ganesh V wrote: > > > > > Hello- > > > > > > I am evaluating HBase for storage of time-series data and see periodic > > > degradation of the cluster happening at the start of the hour, every > > hour, > > > for about 10mins. I see "WALProcedureStoreSyncThread" (wal rolling?) in > > the > > > logs during this time like so: > > > > > > 2016-03-01 06:09:35,151 INFO [WALProcedureStoreSyncThread] > > > wal.WALProcedureStore: Remove log: > > > > > > hdfs://hdmaster01:54310/hbase/MasterProcWALs/state-00000000000000000009.log > > > > > > In my tests, I'm pushing 1million data points (each about 200bytes in > > size) > > > into the cluster each minute at the same time using 5000 threads. I am > > also > > > querying 1000 of these data points each minute to test latency, errors, > > and > > > performance. The cluster runs absolutely fine except for those ~10mins > at > > > the start of every hour when both reads and writes are affected. Could > > > someone suggest which part of HBase needs tuning? Thanks! > > > > > > > > > -Ganesh > > > > > > --001a1141228cc61945052dcf32e4--