Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 48604 invoked from network); 17 Feb 2011 08:38:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2011 08:38:20 -0000 Received: (qmail 24723 invoked by uid 500); 17 Feb 2011 08:38:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 24440 invoked by uid 500); 17 Feb 2011 08:38:14 -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 24424 invoked by uid 99); 17 Feb 2011 08:38:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 08:38:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.160.172] (HELO mail-gy0-f172.google.com) (209.85.160.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Feb 2011 08:38:06 +0000 Received: by gyd12 with SMTP id 12so1107396gyd.31 for ; Thu, 17 Feb 2011 00:37:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.151.148.14 with SMTP id a14mr1991856ybo.410.1297931861203; Thu, 17 Feb 2011 00:37:41 -0800 (PST) Sender: scode@scode.org Received: by 10.150.148.20 with HTTP; Thu, 17 Feb 2011 00:37:41 -0800 (PST) X-Originating-IP: [95.195.117.27] In-Reply-To: References: Date: Thu, 17 Feb 2011 09:37:41 +0100 X-Google-Sender-Auth: 6tmrIK--16vNO56ZHlB0UACam-U Message-ID: Subject: Re: frequent client exceptions on 0.7.0 From: Peter Schuller To: user@cassandra.apache.org Cc: Andy Skalet Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > =C2=A0 raise EOFError() > EOFError [snip] > error: [Errno 104] Connection reset by peer Sounds like you either have a firewalling/networking issues that is tearing down TCP connections, or your cassandra node is dying. Have you checked the Cassandra system log? A frequent mistake is configuring memtables thresholds far too aggressively for your heap size, resulting in an out-of-memory error which, given Cassandra's default JVM options, results in the node dying. Bottom line: Check /var/log/cassandra/system.log to begin with and see if it's reporting anything or being restarted. --=20 / Peter Schuller