Return-Path: 
 <user-return-42278-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 39099111A0
	for <apmail-cassandra-user-archive@www.apache.org>;
 Sun, 10 Aug 2014 01:50:50 +0000 (UTC)
Received: (qmail 66942 invoked by uid 500); 10 Aug 2014 01:50:47 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 66898 invoked by uid 500); 10 Aug 2014 01:50:47 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 66888 invoked by uid 99); 10 Aug 2014 01:50:47 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Aug 2014 01:50:47 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of redmumba@gmail.com designates
 209.85.220.47 as permitted sender)
Received: from [209.85.220.47] (HELO mail-pa0-f47.google.com) (209.85.220.47)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Aug 2014 01:50:22 +0000
Received: by mail-pa0-f47.google.com with SMTP id kx10so9063717pab.6
        for <user@cassandra.apache.org>; Sat, 09 Aug 2014 18:50:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:message-id:in-reply-to:references:subject:mime-version
         :content-type;
        bh=KINkks9pJsIcFDx0sP/novUK9QS6SeBfp30lQc9d6C4=;
        b=WGB19REt070CydTG7hwcv/IeGKwTFLBw+Ck4OiEfPEGA1cX7ax7F1qT11oVoWaVpsi
         lHvCJXnkJMhBmhVVED7lVvTt7aO9wAwr5Qhm1y0s0MW+0mPA6mhPX3G7odWllpJfjkFx
         pXgsyutisISxoihpEFujhNyt0I7Oq4TK1Ixyi00YFdxpHSEkMEY2dGJGnYHDLt+izcCz
         lnP3rhDds2XjRFgGsIEDY8oi2yS3wujao08QravhGPgi3MCYHFtgXYXTIiiTlHbn6Lu+
         6LL/vXRV5AxbyfKhfDYoUCjrkqLUg+gSIXRHtFknVeg5y7CAjhhAWLzM1kjD4r0ZzQKr
         kpVg==
X-Received: by 10.68.225.105 with SMTP id rj9mr33370380pbc.108.1407635420567;
        Sat, 09 Aug 2014 18:50:20 -0700 (PDT)
Received: from amcfague-mac (c-24-19-235-162.hsd1.wa.comcast.net.
 [24.19.235.162])
        by mx.google.com with ESMTPSA id
 ei1sm10951982pdb.20.2014.08.09.18.50.19
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sat, 09 Aug 2014 18:50:19 -0700 (PDT)
Date: Sat, 9 Aug 2014 18:50:18 -0700
From: Andrew <redmumba@gmail.com>
To: Jonathan Haddad <jon@jonhaddad.com>, user@cassandra.apache.org
Message-ID: <etPan.53e6cfdb.3352255a.97fe@amcfague-mac>
In-Reply-To: 
 <CACUnPaBJrWw+UpC0vNFdfEdP7DzGptK2HQRJVU_7SZ=kUQV-3Q@mail.gmail.com>
References: 
 <CAAX2xq6poTKFm52N6Hz7sRNiV_mbuvTSeVuEwmvYvJBCXs0egg@mail.gmail.com>
 <CAK0tFt7x3aGKZybxpQeEztsR+9us5vNFO8fiNX5+FTHEye4G1Q@mail.gmail.com>
 <CAPwXK78KGu+mt=-nVTHwnzt++3dth-5a=ZW_Fk__qyktLSwYiQ@mail.gmail.com>
 <CAAam9sscJdMC3jo5cm7o7XZgw=XsYayb-H9hb18CzYY_Nghh7w@mail.gmail.com>
 <etPan.53e66151.1190cde7.97fe@amcfague-mac>
 <CAAZU44nx7zZ8BtSF3xBbema3gTeF01W80BGzNrZgUWYkaZPxGg@mail.gmail.com>
 <CACUnPaBJrWw+UpC0vNFdfEdP7DzGptK2HQRJVU_7SZ=kUQV-3Q@mail.gmail.com>
Subject: Re: too many open files
X-Mailer: Airmail (247)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="53e6cfdb_109cf92e_97fe"
X-Virus-Checked: Checked by ClamAV on apache.org

--53e6cfdb_109cf92e_97fe
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Yes, that was the problem=E2=80=94I actually knew better, but had briefly=
 overlooked this that when I was doing some refactoring. =C2=A0I am not t=
he OP (although he himself realized his mistake).

if you follow the thread, I was explaining that the Datastax Java driver =
allowed me to basically open a significantly large number of connections =
until the Cassandra server ran out of connections. =C2=A0Tyler was asking=
 for a repro case and requesting that I file a possible bug, if this was =
something that SHOULD have been caught on the client side (via the max co=
nnections client configuration).

Andrew

On August 9, 2014 at 2:17:57 PM, Jonathan Haddad (jon=40jonhaddad.com) wr=
ote:

It really doesn't need to be this complicated. You only need 1 =20
session per application. It's thread safe and manages the connection =20
pool for you. =20

http://www.datastax.com/drivers/java/2.0/com/datastax/driver/core/Session=
.html =20



On Sat, Aug 9, 2014 at 1:29 PM, Kevin Burton <burton=40spinn3r.com> wrote=
: =20
> Another idea to detect this is when the number of open sessions exceeds=
 the =20
> number of threads. =20
> =20
> On Aug 9, 2014 10:59 AM, =22Andrew=22 <redmumba=40gmail.com> wrote: =20
>> =20
>> I just had a generator that (in the incorrect way) had a cluster as a =
=20
>> member variable, and would call .connect() repeatedly. I =5Fthought=5F=
, =20
>> incorrectly, that the Session was thread unsafe, and so I should reque=
st a =20
>> separate Session each time=E2=80=94obviously wrong in hind sight. =20
>> =20
>> There was no special logic; I had a restriction of about 128 connectio=
ns =20
>> per host, but the connections were in the 100s of thousands, like the =
OP =20
>> mentioned. Again, I=E2=80=99ll see about reproducing it on Monday, but=
 just wanted =20
>> the repro steps (overall) to live somewhere in case I can=E2=80=99t. :=
) =20
>> =20
>> Andrew =20
>> =20
>> On August 8, 2014 at 4:08:50 PM, Tyler Hobbs (tyler=40datastax.com) wr=
ote: =20
>> =20
>> =20
>> On =46ri, Aug 8, 2014 at 5:52 PM, Redmumba <redmumba=40gmail.com> wrot=
e: =20
>>> =20
>>> Just to chime in, I also ran into this issue when I was migrating to =
the =20
>>> Datastax client. Instead of reusing the session, I was opening a new =
session =20
>>> each time. =46or some reason, even though I was still closing the ses=
sion on =20
>>> the client side, I was getting the same error. =20
>> =20
>> =20
>> Which driver=3F If you can still reproduce this, would you mind openin=
g a =20
>> ticket=3F (https://datastax-oss.atlassian.net/secure/BrowseProjects.js=
pa=23all) =20
>> =20
>> =20
>> -- =20
>> Tyler Hobbs =20
>> DataStax =20



-- =20
Jon Haddad =20
http://www.rustyrazorblade.com =20
skype: rustyrazorblade =20

--53e6cfdb_109cf92e_97fe
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html><head><style>body=7Bfont-family:Helvetica,Arial;font-size:13px=7D</=
style></head><body style=3D=22word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space;=22><div id=3D=22bloop=5Fcust=
omfont=22 style=3D=22font-family:Helvetica,Arial;font-size:13px; color: r=
gba(0,0,0,1.0); margin: 0px; line-height: auto;=22><div id=3D=22bloop=5Fc=
ustomfont=22 style=3D=22margin: 0px;=22>Yes, that was the problem=E2=80=94=
I actually knew better, but had briefly overlooked this that when I was d=
oing some refactoring. &nbsp;I am not the OP (although he himself realize=
d his mistake).</div><div id=3D=22bloop=5Fcustomfont=22 style=3D=22margin=
: 0px;=22><br></div><div id=3D=22bloop=5Fcustomfont=22 style=3D=22margin:=
 0px;=22>if you follow the thread, I was explaining that the Datastax Jav=
a driver allowed me to basically open a significantly large number of con=
nections until the Cassandra server ran out of connections. &nbsp;Tyler w=
as asking for a repro case and requesting that I file a possible bug, if =
this was something that SHOULD have been caught on the client side (via t=
he max connections client configuration).</div><div id=3D=22bloop=5Fsign=5F=
1407635211959003904=22 class=3D=22bloop=5Fsign=22></div></div> <div id=3D=
=22bloop=5Fsign=5F1407635295872188928=22 class=3D=22bloop=5Fsign=22><div>=
<br></div><span style=3D=22font-family:helvetica,arial;font-size:13px=22>=
</span>Andrew<span></span></div> <br><p style=3D=22color:=23000;=22>On Au=
gust 9, 2014 at 2:17:57 PM, Jonathan Haddad (<a href=3D=22mailto:jon=40jo=
nhaddad.com=22>jon=40jonhaddad.com</a>) wrote:</p> <blockquote type=3D=22=
cite=22 class=3D=22clean=5Fbq=22><span><div><div></div><div>It really doe=
sn't need to be this complicated.  You only need 1
<br>session per application.  It's thread safe and manages the connection=

<br>pool for you.
<br>
<br>http://www.datastax.com/drivers/java/2.0/com/datastax/driver/core/Ses=
sion.html
<br>
<br>
<br>
<br>On Sat, Aug 9, 2014 at 1:29 PM, Kevin Burton &lt;burton=40spinn3r.com=
&gt; wrote:
<br>&gt; Another idea to detect this is when the number of open sessions =
exceeds the
<br>&gt; number of threads.
<br>&gt;
<br>&gt; On Aug 9, 2014 10:59 AM, =22Andrew=22 &lt;redmumba=40gmail.com&g=
t; wrote:
<br>&gt;&gt;
<br>&gt;&gt; I just had a generator that (in the incorrect way) had a clu=
ster as a
<br>&gt;&gt; member variable, and would call .connect() repeatedly.  I =5F=
thought=5F,
<br>&gt;&gt; incorrectly, that the Session was thread unsafe, and so I sh=
ould request a
<br>&gt;&gt; separate Session each time=E2=80=94obviously wrong in hind s=
ight.
<br>&gt;&gt;
<br>&gt;&gt; There was no special logic; I had a restriction of about 128=
 connections
<br>&gt;&gt; per host, but the connections were in the 100s of thousands,=
 like the OP
<br>&gt;&gt; mentioned.  Again, I=E2=80=99ll see about reproducing it on =
Monday, but just wanted
<br>&gt;&gt; the repro steps (overall) to live somewhere in case I can=E2=
=80=99t. :)
<br>&gt;&gt;
<br>&gt;&gt; Andrew
<br>&gt;&gt;
<br>&gt;&gt; On August 8, 2014 at 4:08:50 PM, Tyler Hobbs (tyler=40datast=
ax.com) wrote:
<br>&gt;&gt;
<br>&gt;&gt;
<br>&gt;&gt; On =46ri, Aug 8, 2014 at 5:52 PM, Redmumba &lt;redmumba=40gm=
ail.com&gt; wrote:
<br>&gt;&gt;&gt;
<br>&gt;&gt;&gt; Just to chime in, I also ran into this issue when I was =
migrating to the
<br>&gt;&gt;&gt; Datastax client. Instead of reusing the session, I was o=
pening a new session
<br>&gt;&gt;&gt; each time. =46or some reason, even though I was still cl=
osing the session on
<br>&gt;&gt;&gt; the client side, I was getting the same error.
<br>&gt;&gt;
<br>&gt;&gt;
<br>&gt;&gt; Which driver=3F  If you can still reproduce this, would you =
mind opening a
<br>&gt;&gt; ticket=3F (https://datastax-oss.atlassian.net/secure/BrowseP=
rojects.jspa=23all)
<br>&gt;&gt;
<br>&gt;&gt;
<br>&gt;&gt; --
<br>&gt;&gt; Tyler Hobbs
<br>&gt;&gt; DataStax
<br>
<br>
<br>
<br>-- =20
<br>Jon Haddad
<br>http://www.rustyrazorblade.com
<br>skype: rustyrazorblade
<br></div></div></span></blockquote></body></html>
--53e6cfdb_109cf92e_97fe--