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 Janne.Jalkanen@ecyrd.com
 designates 87.108.86.67 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Lots of 0 Bytes tmp Data/Index files remain in data folder
From: Janne Jalkanen <Janne.Jalkanen@ecyrd.com>
In-Reply-To: <1328834981769-7271286.post@n2.nabble.com>
Date: Fri, 10 Feb 2012 09:50:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB00D036-BDBA-4684-ABA3-64180E4B1A75@ecyrd.com>
References: <1328834981769-7271286.post@n2.nabble.com>
To: user@cassandra.apache.org


Yup, that's exactly it. You can get rid of those either by restarting =
the node or upgrading to 1.0.7.

/Janne

On Feb 10, 2012, at 02:49 , Roshan wrote:

> I have deployed 2 node Cassandra 1.0.6 cluster in production and it =
running
> almost t weeks without any issue. But I can see lots of (more than 90) =
0
> bytes tmp data and index files in the data directory.=20
>=20
> So far this is not a issue for me, but want to know why is that. Seems =
like
> this data/index tmp files getting create with every compaction (but =
not
> sure).=20
>=20
> Are there any relationship with this issue
> https://issues.apache.org/jira/browse/CASSANDRA-3616 ?
>=20
> Could someone please clarify this to me. Thanks.=20
>=20
> --
> View this message in context: =
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Lots-of-0=
-Bytes-tmp-Data-Index-files-remain-in-data-folder-tp7271286p7271286.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive =
at Nabble.com.