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 9075810713 for ; Fri, 18 Apr 2014 08:55:13 +0000 (UTC) Received: (qmail 52928 invoked by uid 500); 18 Apr 2014 04:51:10 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 52475 invoked by uid 500); 18 Apr 2014 04:51:09 -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 52458 invoked by uid 99); 18 Apr 2014 04:51:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 04:51:06 +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 saint.ack@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qc0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 04:51:01 +0000 Received: by mail-qc0-f175.google.com with SMTP id e16so1308075qcx.6 for ; Thu, 17 Apr 2014 21:50:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=z3XS3rCZ1YrCH3r2HnPeyP6LaHPLhqkDUJVf5q5eAWo=; b=GZs/fIzxV3qtfoxAuAVQNkuBq+hq0XpBPLSIknyrbbd1Ncmcj53pC5kJXBtdQgkqXP 3By5Hatxobb+Uq3JU3Ygptq9qiuYn1vUPIZMn+VjBSjzuY4Hw2O4dUE7yZ2a0hmWESf4 JcJd7lMR11sB7sDI9SBulVpBh5h031ZnVDbhMq7yGLp2P2AMIJabSh/J8uiyOl1XcEtV qQinW6o9Cfgi8npBzmIqJ/Ao23I/p268rIDgjagagQjUVLFrhnnkV88vzcUuaO8k6RO7 OOZ6g0r2UPX0YPVKnkkmMVPzcs0A3zzGMoLTE4MfY6CHsK/WgrbbUYwP0YJzuYycRlny 5msQ== MIME-Version: 1.0 X-Received: by 10.140.22.113 with SMTP id 104mr22126675qgm.56.1397796640353; Thu, 17 Apr 2014 21:50:40 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.96.183.230 with HTTP; Thu, 17 Apr 2014 21:50:40 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Apr 2014 21:50:40 -0700 X-Google-Sender-Auth: -7GCEFM-te_ObYAbz7WhVeg2eK0 Message-ID: Subject: Re: taking snapshot's creates to many TCP CLOSE_WAIT handles on the hbase master server From: Stack To: Hbase-User Content-Type: multipart/alternative; boundary=001a11c1157437723c04f749e4cb X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1157437723c04f749e4cb Content-Type: text/plain; charset=UTF-8 On Thu, Apr 17, 2014 at 6:51 AM, Hansi Klose wrote: > Hi, > > we use a script to take on a regular basis snapshot's and delete old one's. > > We recognizes that the web interface of the hbase master was not working > any more becaues of too many open files. > > The master reaches his number of open file limit of 32768 > > When I run lsof I saw that there where a lot of TCP CLOSE_WAIT handles open > with the regionserver as target. > > On the regionserver there is just one connection to the hbase master. > > I can see that the count of the CLOSE_WAIT handles grow each time > i take a snapshot. When i delete on nothing changes. > Each time i take a snapshot there are 20 - 30 new CLOSE_WAIT handles. > > Why does the master do not close the handles? Is there a parameter > with a timeout we can use? > > We use hbase 0.94.2-cdh4.2.0. > Does https://issues.apache.org/jira/browse/HBASE-9393?jql=text%20~%20%22CLOSE_WAIT%22help? In particular, what happens if you up the socket cache as suggested on the end of the issue? St.Ack --001a11c1157437723c04f749e4cb--