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 D16D1F97C for ; Thu, 21 Mar 2013 00:50:53 +0000 (UTC) Received: (qmail 38747 invoked by uid 500); 21 Mar 2013 00:50:51 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 38730 invoked by uid 500); 21 Mar 2013 00:50:51 -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 38721 invoked by uid 99); 21 Mar 2013 00:50:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 00:50:50 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ajazam@gmail.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-la0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 00:50:45 +0000 Received: by mail-la0-f49.google.com with SMTP id fs13so4053115lab.8 for ; Wed, 20 Mar 2013 17:50:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=6KU6EVO607uRTSV/9t5LUMHmggC+8sLYXrV2HKNVdDA=; b=Bl2ZAxCbi7n9rWEZt01luwqaxnYVYoUeVSqSEUm8B4gZ0EU68VAAgjQ5GA2j2syTRw t/G1JZUQCprfR4zj/w9FOgZSs5eqK3CiPQSkCj/OD83JmyC1zTF6cA07Lkbfgkfew8L6 23J2V9EKR/i6UVOlITzExbesGWg9UkUHdcIzhI16io2jSURGCUJXSM7iHeLgq3mpy4xS tVZIJ5EOnWiO25F8hGk9+t0tqVckhezplhMN+WA6DVr7OQT7vtvm23WCoGsWJ/RvQBQI HUWSddm+fFVHW9UDg8HEyQopsmxC/vOcGnOkInteBb7M1gSIVg/nxdaW7KZQ8OZY1hRr uepQ== MIME-Version: 1.0 X-Received: by 10.112.87.105 with SMTP id w9mr10197717lbz.14.1363827024860; Wed, 20 Mar 2013 17:50:24 -0700 (PDT) Received: by 10.112.19.10 with HTTP; Wed, 20 Mar 2013 17:50:24 -0700 (PDT) Received: by 10.112.19.10 with HTTP; Wed, 20 Mar 2013 17:50:24 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Mar 2013 00:50:24 +0000 Message-ID: Subject: RE: java.lang.OutOfMemoryError: unable to create new native thread From: Jabbar Azam To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec554e1065a22b604d864b992 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554e1065a22b604d864b992 Content-Type: text/plain; charset=ISO-8859-1 Hello, Also have a look at http://www.datastax.com/docs/1.2/install/recommended_settings On 21 Mar 2013 00:06, "S C" wrote: > Apparently max user process was set very low on the machine. > > How to check? > ulimit -u > > Set it to unlimited /etc/security/limits.conf > > * soft nprocs unlimited > * hard nprocs unlimited > > > > ------------------------------ > From: asf11@outlook.com > To: user@cassandra.apache.org > Subject: RE: java.lang.OutOfMemoryError: unable to create new native thread > Date: Fri, 15 Mar 2013 18:57:05 -0500 > > I think I figured out where the issue is. I will keep you posted soon. > > ------------------------------ > From: asf11@outlook.com > To: user@cassandra.apache.org > Subject: java.lang.OutOfMemoryError: unable to create new native thread > Date: Fri, 15 Mar 2013 17:54:25 -0500 > > I have a Cassandra node that is going down frequently with > 'java.lang.OutOfMemoryError: unable to create new native thread". Its a > 16GB VM out of which 4GB is set as Xmx and there are no other process > running on the VM. I have about 300 clients connecting to this node on an > average. I have no indication from vmstats/SAR that my VM has used more > memory or is memory hungry. Doesn't indicate a memory issue to > me. Appreciate any pointers to this. > > System Specs: > 2CPU > 16GB > RHEL 6.2 > > > Thank you. > --bcaec554e1065a22b604d864b992 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hello,
Also have a look at http://www.datastax.com/docs/1.2/install/recommended_set= tings

On 21 Mar 2013 00:06, "S C" <asf11@outlook.com> wrote:
Apparently max user process was set very low on the machin= e.

How to check?
ulimit -u

Set it to unlimited /etc/security/limits.conf

* soft nprocs unlimited
* hard nprocs unlimited



From: asf11@outlook.com
To: user@cassandra.apache.org Subject: RE: java.lang.OutOfMemoryError: unable to create new native thread=
Date: Fri, 15 Mar 2013 18:57:05 -0500

I think I figured out where the issue is. I will keep you = posted soon.


From: asf11@outlook.com
To: user@cassandra.apache.org Subject: java.lang.OutOfMemoryError: unable to create new native thread
= Date: Fri, 15 Mar 2013 17:54:25 -0500

I have a Cassandra node that is going down frequently with= 'java.lang.OutOfMemoryError: unable to create new native thread".= Its a 16GB VM out of which 4GB is set as Xmx and there are no other proces= s running on the VM. =A0I have about 300 clients connecting to this node on= an average. I have no indication from vmstats/SAR that my VM has used more= memory or is memory hungry. Doesn't indicate a memory issue to me.=A0A= ppreciate any pointers to this.

System Specs:=A0
2CPU
16GB
RHE= L 6.2


Thank you.<= /span>
--bcaec554e1065a22b604d864b992--