Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of mor.yuki@gmail.com designates
 209.85.160.172 as permitted sender)
Date: Fri, 17 Feb 2012 11:36:03 -0600
From: Yuki Morishita <mor.yuki@gmail.com>
To: user@cassandra.apache.org
Message-ID: <B3F5DD3C29B949DFB886D8F0C75E0D95@gmail.com>
In-Reply-To: <4F3E45A1.3020801@opera.com>
References: <4F3E45A1.3020801@opera.com>
Subject: Re: Streaming sessions from BulkOutputFormat job being listed
 long after they were killed
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f3e9003_520eedd1_cc"

--4f3e9003_520eedd1_cc
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Erik,

Currently, streaming failure handling is poorly functioning. 
There are several discussions and bug reports regarding streaming failure on jira.

Hanged streaming session will be left in memory unless you restart C*, but it does not cause problem I believe. 

-- 
Yuki Morishita


On Friday, February 17, 2012 at 6:18 AM, Erik Forsberg wrote:

> Hi!
> 
> If I run a hadoop job that uses BulkOutputFormat to write data to 
> Cassandra, and that hadoop job is aborted, i.e. streaming sessions are 
> not completed, it seems like the streaming sessions hang around for a 
> very long time, I've observed at least 12-15h, in output from 'nodetool 
> netstats'.
> 
> To me it seems like they go away only after a restart of Cassandra.
> 
> Is this a known behaviour? Does it cause any problems, f. ex. consuming 
> memory, or should I just ignore it?
> 
> Regards,
> \EF
> 
> 


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


                <div>
                    Erik,</div><div><br></div><div>Currently, streaming f=
ailure handling is poorly functioning.&nbsp;</div><div>There are several =
discussions and bug reports regarding streaming failure on jira.</div><di=
v><br></div><div>Hanged streaming session will be left in memory unless y=
ou restart C*, but it does not cause problem I believe.</div>
                <div><div><br></div><div>--&nbsp;</div><div>Yuki Morishit=
a</div><div><br></div></div>
                =20
                <p style=3D=22color: =23A0A0A8;=22>On =46riday, =46ebruar=
y 17, 2012 at 6:18 AM, Erik =46orsberg wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div><div>Hi=21</div><div><br></div><div>I=
f I run a hadoop job that uses BulkOutput=46ormat to write data to </div>=
<div>Cassandra, and that hadoop job is aborted, i.e. streaming sessions a=
re </div><div>not completed, it seems like the streaming sessions hang ar=
ound for a </div><div>very long time, I've observed at least 12-15h, in o=
utput from 'nodetool </div><div>netstats'.</div><div><br></div><div>To me=
 it seems like they go away only after a restart of Cassandra.</div><div>=
<br></div><div>Is this a known behaviour=3F Does it cause any problems, f=
. ex. consuming </div><div>memory, or should I just ignore it=3F</div><di=
v><br></div><div>Regards,</div><div>=5CE=46</div></div></div></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
            
--4f3e9003_520eedd1_cc--