Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 20143 invoked from network); 12 May 2010 15:26:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 15:26:19 -0000 Received: (qmail 40186 invoked by uid 500); 12 May 2010 15:26:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 40119 invoked by uid 500); 12 May 2010 15:26:18 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 40111 invoked by uid 99); 12 May 2010 15:26:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 15:26:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=AWL,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of izquierdo@strands.com) Received: from [217.116.18.226] (HELO mail.strands.com) (217.116.18.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 15:26:10 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.strands.com (Postfix) with ESMTP id B59EA2CC498 for ; Wed, 12 May 2010 17:24:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at strands.com X-Spam-Score: -11 X-Spam-Level: Received: from mail.strands.com ([127.0.0.1]) by localhost (mail.strands.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqXko1eCgR4K for ; Wed, 12 May 2010 17:24:58 +0200 (CEST) Received: from [192.168.1.119] (mad-jazztel [87.216.56.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: izquierdo) by mail.strands.com (Postfix) with ESMTPSA id AD2132CC45A for ; Wed, 12 May 2010 17:24:57 +0200 (CEST) Message-ID: <4BEAC868.4060401@strands.com> Date: Wed, 12 May 2010 17:25:28 +0200 From: =?ISO-8859-1?Q?H=E9ctor_Izquierdo?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Lightning/1.0b1 Shredder/3.0.3pre MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: timeout while running simple hadoop job References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Old-Spam-Flag: NO X-Old-Spam-Status: No, score=-11 required=5.1 tests=[ALL_TRUSTED=-5.5, BAYES_00=-5.5] autolearn=ham Have you checked your open file handler limit? You can do that by using "ulimit" in the shell. If it's too low, you will encounter the "too many open files" error. You can also see how many open handlers an application has with "lsof". H�ctor Izquierdo On 12/05/10 17:00, gabriele renzi wrote: > On Wed, May 12, 2010 at 4:43 PM, Jonathan Ellis wrote: > >> On Wed, May 12, 2010 at 5:11 AM, gabriele renzi wrote: >> >>> - is it possible that such errors show up on the client side as >>> timeoutErrors when they could be reported better? >>> >> No, if the node the client is talking to doesn't get a reply from the >> data node, there is no way for it to magically find out what happened >> since ipso facto it got no reply. >> > Sorry I was not clear: I meant the first error (where we get a > RuntimeException in reading the file, not in the socket.accept()). > There we have a reasonable error message (either "too many open files" > or "corrupt sstable") that does not appear client side. > > > >