Return-Path: 
 <hbase-user-return-3736-apmail-hadoop-hbase-user-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org
Received: (qmail 15286 invoked from network); 2 Apr 2009 23:43:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 2 Apr 2009 23:43:13 -0000
Received: (qmail 20637 invoked by uid 500); 2 Apr 2009 23:43:12 -0000
Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org
Received: (qmail 20587 invoked by uid 500); 2 Apr 2009 23:43:12 -0000
Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hbase-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hbase-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hbase-user@hadoop.apache.org>
List-Id: <hbase-user.hadoop.apache.org>
Reply-To: hbase-user@hadoop.apache.org
Delivered-To: mailing list hbase-user@hadoop.apache.org
Received: (qmail 20577 invoked by uid 99); 2 Apr 2009 23:43:12 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 23:43:12 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [76.13.9.50] (HELO web65506.mail.ac4.yahoo.com) (76.13.9.50)
    by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Apr 2009 23:43:04 +0000
Received: (qmail 10299 invoked by uid 60001); 2 Apr 2009 23:42:43 -0000
Message-ID: <156193.10114.qm@web65506.mail.ac4.yahoo.com>
X-YMail-OSG: 
 2zaHhDAVM1nEXc_e_w84yw_U8qFZrmj.6jnBe9zwhq0DOANTlbWeRalChEQm5jv95tzsCoQ_KCRYSnuNE3CsdpDVt3nL2LDUjJlYTr.wC.bkW.a69XTPLN3hZWtHoTGdl8XTsTtKUngieIrD13U.hgvja5uB.aY7x3ygThg7FeBhtlVVWpWuzIB3IVPf4uHEq2EYfPg3m3XtEGFiPRfZn97JbLvpuQS234F3MH6aiJRbRICSBlEsg91BeeDnTL9.SsON9dYgwjBq7s6FKydLJpwgWDGVD_.NG4R9ADxRj_JI8nbd750zR40_1j6IYQy4FkE_mH7xDQm.wAPaOc5buLY-
Received: from [69.108.155.182] by web65506.mail.ac4.yahoo.com via HTTP;
 Thu, 02 Apr 2009 16:42:43 PDT
X-RocketYMMF: apurtell
X-Mailer: YahooMailWebService/0.7.289.1
Date: Thu, 2 Apr 2009 16:42:43 -0700 (PDT)
From: Andrew Purtell <apurtell@apache.org>
Reply-To: apurtell@apache.org
Subject: Re: Monitoring xceivers
To: hbase-user@hadoop.apache.org
In-Reply-To: <2f81e00904020629s360264e1g24577a7379277e28@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Checked: Checked by ClamAV on apache.org


Yes.

This could be a nice way to do this. Please let us know if this
approach works for you.

   - Andy


> From: Michael Dagaev <michael.dagaev@gmail.com>
> Subject: Monitoring xceivers
> To: hbase-user@hadoop.apache.org
> Date: Thursday, April 2, 2009, 6:29 AM
> Hi, all
> 
>        I heard from somebody on the list that the xceivers
> number is actually the number of worker threads of the data
> node process.
> 
> Assuming Java uses native threads we can monitor the number
> of xceivers just by ls /proc/<data node pid>/task | wc -l and
> if it is getting to the limit, add data  nodes.
> 
> Does it make sense?
> M.