Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05E64177B3 for ; Wed, 1 Oct 2014 17:51:37 +0000 (UTC) Received: (qmail 41328 invoked by uid 500); 1 Oct 2014 17:51:36 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 41246 invoked by uid 500); 1 Oct 2014 17:51:36 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 41234 invoked by uid 99); 1 Oct 2014 17:51:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Oct 2014 17:51:35 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.216.182 as permitted sender) Received: from [209.85.216.182] (HELO mail-qc0-f182.google.com) (209.85.216.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Oct 2014 17:51:30 +0000 Received: by mail-qc0-f182.google.com with SMTP id i17so808592qcy.13 for ; Wed, 01 Oct 2014 10:51:09 -0700 (PDT) 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 :content-type; bh=zi3eRrRD+tw0/ljmxyL5EpReeVIX41/0e2Vm/zY6T44=; b=kdXm8JTnPa4Sug64kozWU8vsXMzkYWLDNDuMas0eO4ckipxjV9q2amVMEg2AOvxfRa YMolLaJ5NnFk1osc1tCNBOTktfChVVTaHwxNXCOHC2Uc4JFVvjs9zunXKe19BB+H5YBf NHtrIHk19C2OoNKiCUpJ+uZdYQJ8Cxam8W7q65rSA5GrfRBTMs6u17EBX2Cy8uEzUhzn Wof0HAA5oRv/sq9RyTOajl2xNnw4x1RS7qoLgDYx3RT6TQMUv+apDAd4HR6oG7rq/du2 Kce0a5eB6vOJzCRZoVlNCjZuLGN4nOf9tKPOUIGz1HomwBlANE2ZoOowT7QEsndzi5VF 6zHQ== MIME-Version: 1.0 X-Received: by 10.236.231.39 with SMTP id k37mr78077577yhq.32.1412185869596; Wed, 01 Oct 2014 10:51:09 -0700 (PDT) Received: by 10.170.163.70 with HTTP; Wed, 1 Oct 2014 10:51:09 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Oct 2014 10:51:09 -0700 Message-ID: Subject: Re: WARN messages clarifications From: Ted Yu To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=089e0103e7301d3bb2050460258d X-Virus-Checked: Checked by ClamAV on apache.org --089e0103e7301d3bb2050460258d Content-Type: text/plain; charset=UTF-8 Suppose your OutlierHTable was communicating with a region server which happened to go through GC pause. The query would exhibit longer duration compared to one where no region server goes through GC (assuming other factors being equal: network traffic, size of data queried, etc). bq. Is GC pause set on a timer? I don't think so. It depends on the load region server handles. Cheers On Wed, Oct 1, 2014 at 10:37 AM, Jinal Shah wrote: > Is GC pause set on a timer? How much does that impact the query request? > > On Wed, Oct 1, 2014 at 10:48 AM, Ted Yu wrote: > > > One other possibility would be the region server going through GC pause. > > > > Cheers > > > > On Wed, Oct 1, 2014 at 8:04 AM, Jinal Shah > > wrote: > > > > > We are using 0.94.15 version. > > > > > > On Wed, Oct 1, 2014 at 10:03 AM, Ted Yu wrote: > > > > > > > I searched 0.94 and 0.98 code base but didn't find the message below. > > > > > > > > Which version of HBase are you using ? > > > > > > > > Cheers > > > > > > > > On Wed, Oct 1, 2014 at 7:58 AM, Jinal Shah > > > > wrote: > > > > > > > > > Hi everyone > > > > > > > > > > We are seeing these WARN log messages from this class > > > > > > > > > > > > > > > com.cerner.hbase.extensions.OutlierHTableInterceptorFactory$OutlierHTable. > > > > > It normally happens when the query takes a long time to execute and > > > > > displays the duration as well like this > > > > > > > > > > Duration Threshold exceeded: [durationThreshold=1000] > > > > > Actuals: [actualBatchSize=1: actualPayloadSize=0: > > actualDuration=3929] > > > > > > > > > > The scenarios I found for the delay are > > > > > > > > > > > > > > > - Network issues taking time for delays > > > > > - Trying to establish a connection for the first time > > > > > - Some component failures occurred like Zookeeper node when down > > or > > > > > Master failed over. > > > > > > > > > > > > > > > So can someone give say what other possible scenarios for delays in > > > > > executing a query. > > > > > > > > > > Thanks > > > > > Jinal > > > > > > > > > > > > > > > --089e0103e7301d3bb2050460258d--