Return-Path: X-Original-To: apmail-flume-user-archive@www.apache.org Delivered-To: apmail-flume-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 F423511174 for ; Sat, 20 Sep 2014 21:34:47 +0000 (UTC) Received: (qmail 35422 invoked by uid 500); 20 Sep 2014 21:34:47 -0000 Delivered-To: apmail-flume-user-archive@flume.apache.org Received: (qmail 35367 invoked by uid 500); 20 Sep 2014 21:34:47 -0000 Mailing-List: contact user-help@flume.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flume.apache.org Delivered-To: mailing list user@flume.apache.org Received: (qmail 35357 invoked by uid 99); 20 Sep 2014 21:34:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Sep 2014 21:34:47 +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 (nike.apache.org: domain of terreyshih@gmail.com designates 209.85.192.181 as permitted sender) Received: from [209.85.192.181] (HELO mail-pd0-f181.google.com) (209.85.192.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Sep 2014 21:34:19 +0000 Received: by mail-pd0-f181.google.com with SMTP id r10so2059760pdi.40 for ; Sat, 20 Sep 2014 14:34:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=SoeRuND9pHVBytaPE6jFynDc/eqAghpBQeo/JCPaNNI=; b=sI10ws3GGtVMmn5749JhmLLa5lNN/Yme0EVND8LTm/BU09ycenAsrL+oSm0EOqPKmO T1146x0mcBv7/XA2neXaSY7C6a5TE6ECHWv7dNG98W8a9UxAn2Kf88vTfjI/r36Tv8Sl vIixmxYBt9038SMLIL2pGOA28P7RIaSjbgFAu41Sml5wXpgS4Ksz7+2/jcrEa1/nWvWr mXfCXaY+HOy+MESs/O+oB3EI0kzWyKPjzTnbAv9dDE1aPNJypC05qZgNuCnFXlGkMTxj ooWi5vlOwn1BkfmFn1dzGs2wys+U8PDmrkzrjggNns0svsYrqXX+TeXy1sh5BIke9anX dslQ== X-Received: by 10.68.69.70 with SMTP id c6mr11704624pbu.111.1411248858398; Sat, 20 Sep 2014 14:34:18 -0700 (PDT) Received: from [192.168.0.209] (99-162-148-175.lightspeed.sntcca.sbcglobal.net. [99.162.148.175]) by mx.google.com with ESMTPSA id zf5sm5331964pbc.44.2014.09.20.14.34.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Sep 2014 14:34:17 -0700 (PDT) From: terreyshih Content-Type: multipart/alternative; boundary="Apple-Mail=_03134518-8C73-41EA-973B-FEF9A5D7C332" Subject: flume agent / JVM crashes periodically Message-Id: <63720C54-041A-4D27-B6A7-9EF03680F027@gmail.com> Date: Sat, 20 Sep 2014 14:33:55 -0700 To: user@flume.apache.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_03134518-8C73-41EA-973B-FEF9A5D7C332 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi, I am having a lot of difficulty trying to debug an issue. The flume = server stops working after a few hours and the JVM shuts down. The = snippet of the message I got in the log starts with following: 20 Sep 2014 12:24:10,899 DEBUG [New I/O worker #9] = (org.hbase.async.RegionClient.decode:1349) - ------------------<< = LEAVING DECODE <<------------------ time elapsed: 75us 20 Sep 2014 12:24:19,942 INFO [agent-shutdown-hook] = (org.apache.flume.lifecycle.LifecycleSupervisor.stop:79) - Stopping = lifecycle supervisor 13 20 Sep 2014 12:24:19,943 INFO [agent-shutdown-hook] = (org.apache.flume.instrumentation.MonitoredCounterGroup.stop:149) - = Component type: CHANNEL, name: myChannelC stopped =46rom there it starts to shut down all the channels and eventually the = JVM shuts down. I am running the agent in debug mode and I can see my data coming in = correctly for a couple of hours and the snippet shows, flume enters the = =93LEAVING DECODE=94 section of the flume debug engine. I am writing = the data to HBase sinks by using AsycnHBase. I would appreciate it if someone can help me with this. This is = reproducible around every 2 hours. When does the agent-shutdown-hook gets triggered ? thanks= --Apple-Mail=_03134518-8C73-41EA-973B-FEF9A5D7C332 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Hi,

I am having a lot = of difficulty trying to debug an issue.  The flume server stops = working after a few hours and the JVM shuts down.  The snippet of = the message I got in the log starts with = following:


20 Sep 2014 12:24:10,899 DEBUG [New I/O  worker #9] = (org.hbase.async.RegionClient.decode:1349)  - = ------------------<< LEAVING  DECODE = <<------------------ time elapsed: 75us
20 Sep 2014 12:24:19,942 INFO  [agent-shutdown-hook] = (org.apache.flume.lifecycle.LifecycleSupervisor.stop:79)  - = Stopping lifecycle supervisor 13
20 Sep 2014 12:24:19,943 = INFO  [agent-shutdown-hook] = (org.apache.flume.instrumentation.MonitoredCounterGroup.stop:149)  = - Component type: CHANNEL, name: myChannelC = stopped


=46rom there it = starts to shut down all the channels and eventually the JVM shuts = down.

I am running the agent in debug mode and = I can see my data coming in correctly for a couple of hours and the = snippet shows, flume enters the =93LEAVING DECODE=94 section of the = flume debug engine.  I am writing the data to HBase sinks by using = AsycnHBase.

I would appreciate it if someone = can help me with this.  This is reproducible around every 2 = hours.

When does the agent-shutdown-hook gets = triggered ?

thanks
= --Apple-Mail=_03134518-8C73-41EA-973B-FEF9A5D7C332--