Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of tbarbugli@gmail.com designates
 209.85.212.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd1=WC+x4PvyV4xe8B8ZhG-=xFzV9zpf2_2E-xcEtEbBaA@mail.gmail.com>
References: <5363496A.8000006@dg6obo.de>
	<53634F6B.1040709@gmail.com>
	<53635362.4090902@dg6obo.de>
	<53635A86.4030105@openmarket.com>
	<CAMwLmJaxgO0zFY-2sQOJWKr+eb-E7WkmneeUtk-oSuXB2Jje+w@mail.gmail.com>
	<CAEDUwd1=WC+x4PvyV4xe8B8ZhG-=xFzV9zpf2_2E-xcEtEbBaA@mail.gmail.com>
Date: Fri, 2 May 2014 19:14:46 +0200
Message-ID: 
 <CAMwLmJYbazQ95BVEzzg5GXwq0Aq5US3ohhrQT4bYcMdzVFnwMA@mail.gmail.com>
Subject: Re: Backup procedure
From: tommaso barbugli <tbarbugli@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11c26ab419c28104f86deb73

--001a11c26ab419c28104f86deb73
Content-Type: text/plain; charset=UTF-8

In my tests compressing with lzop sstables (with cassandra compression
turned on) resulted in approx. 50% smaller files.
Thats probably because the chunks of data compressed by lzop are way bigger
than the average size of writes performed on Cassandra (not sure how data
is compressed but I guess it is done per single cell so unless one stores)


2014-05-02 19:01 GMT+02:00 Robert Coli <rcoli@eventbrite.com>:

> On Fri, May 2, 2014 at 2:07 AM, tommaso barbugli <tbarbugli@gmail.com>wrote:
>
>> If you are thinking about using Amazon S3 storage I wrote a tool that
>> performs snapshots and backups on multiple nodes.
>> Backups are stored compressed on S3.
>> https://github.com/tbarbugli/cassandra_snapshotter
>>
>
> https://github.com/JeremyGrosser/tablesnap
>
> SSTables in Cassandra are compressed by default, if you are re-compressing
> them you may just be wasting CPU.. :)
>
> =Rob
>
>

--001a11c26ab419c28104f86deb73
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">In my tests compressing with lz=
op sstables (with cassandra compression turned on) resulted in approx. 50% =
smaller files.</div><div class=3D"gmail_extra">Thats probably because the c=
hunks of data compressed by lzop are way bigger than the average size of wr=
ites performed on Cassandra (not sure how data is compressed but I guess it=
 is done per single cell so unless one stores)</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">2014-05-02 19:01 GMT+02:00 Robert Coli <span dir=3D"ltr=
">&lt;<a href=3D"mailto:rcoli@eventbrite.com" target=3D"_blank">rcoli@event=
brite.com</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D"">On Fri, May 2, 2014 at 2:07 AM, =
tommaso barbugli <span dir=3D"ltr">&lt;<a href=3D"mailto:tbarbugli@gmail.co=
m" target=3D"_blank">tbarbugli@gmail.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr">If you are thinking about using Amazon S3=
 storage I wrote a tool that performs snapshots and backups on multiple nod=
es.=C2=A0<div>


Backups are stored compressed on S3. <a href=3D"https://github.com/tbarbugl=
i/cassandra_snapshotter" target=3D"_blank">https://github.com/tbarbugli/cas=
sandra_snapshotter</a></div></div></blockquote><div><br></div></div><div><a=
 href=3D"https://github.com/JeremyGrosser/tablesnap" target=3D"_blank">http=
s://github.com/JeremyGrosser/tablesnap</a></div>


<div><br></div><div>SSTables in Cassandra are compressed by default, if you=
 are re-compressing them you may just be wasting CPU.. :)</div><div><br></d=
iv><div>=3DRob</div><div><br></div></div></div></div>
</blockquote></div><br></div></div>

--001a11c26ab419c28104f86deb73--