Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-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 6F6F03BDD for ; Thu, 28 Apr 2011 17:25:59 +0000 (UTC) Received: (qmail 76525 invoked by uid 500); 28 Apr 2011 17:25:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 76496 invoked by uid 500); 28 Apr 2011 17:25:57 -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 76488 invoked by uid 99); 28 Apr 2011 17:25:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 17:25:57 +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.161.44] (HELO mail-fx0-f44.google.com) (209.85.161.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2011 17:25:49 +0000 Received: by fxm15 with SMTP id 15so2308301fxm.31 for ; Thu, 28 Apr 2011 10:25:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.159.14 with SMTP id h14mr637546fax.20.1304011527313; Thu, 28 Apr 2011 10:25:27 -0700 (PDT) Sender: scode@scode.org Received: by 10.223.112.79 with HTTP; Thu, 28 Apr 2011 10:25:27 -0700 (PDT) X-Originating-IP: [90.233.35.57] In-Reply-To: References: <148621303477253@web19.yandex.ru> <634081303734063@web116.yandex.ru> <42741303907567@web44.yandex.ru> <594E4B4C-A8B6-40E3-85D9-0D253A55D8DC@thelastpickle.com> Date: Thu, 28 Apr 2011 19:25:27 +0200 X-Google-Sender-Auth: TdMw8dJhsgIJK65Zb85DWfDHzzo Message-ID: Subject: Re: OOM on heavy write load From: Peter Schuller To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 > Could this be related as well to > https://issues.apache.org/jira/browse/CASSANDRA-2463? My gut feel: Maybe, if the slowness/timeouts reported by the OP are intermixed with periods of activity to indicate compacting full gc. OP: Check if cassandra is going into 100% (not less, not more) CPU usage during periods of timeouts. If the huge allocations fail due to fragmentation and fallback to Full GC that might be an expected result. Else -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps. -- / Peter Schuller