Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
In-Reply-To: <CA+BDQ7yjVzrqZj1Jjc_R6gtLYsJ_Bg+ogLXkhN1aTOHz3LHOgw@mail.gmail.com>
References: <CA+BDQ7yjVzrqZj1Jjc_R6gtLYsJ_Bg+ogLXkhN1aTOHz3LHOgw@mail.gmail.com>
From: Chris Lohfink <clohfink85@gmail.com>
Date: Fri, 24 Feb 2017 18:25:12 -0600
Message-ID: <CAOsmgAwJ74VJMib6UyenaYkupKe=w78kf8-txBjhB24auhuiEg@mail.gmail.com>
Subject: Re: partition sizes reported by nodetool tablehistograms
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a1137b2c030a94105494fe1ee
archived-at: Sat, 25 Feb 2017 00:25:18 -0000

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

Its the decompressed size of the partitions. Each sstable has stats
component that contains histograms for the size and number of columns in
the partitions (among other things, can see with sstablemetadata tool),
tablehistograms merges it for each sstable and gives the results.

Chris

On Fri, Feb 24, 2017 at 4:53 PM, John Sanda <john.sanda@gmail.com> wrote:

> I am working on some issues involving really big partitions. I have been
> making extensive use of nodetool tablehistograms. What exactly is the
> partition size being reported? I have a table for which the max value
> reported is about 3.5 GB, but running du -h against the table data
> directory reports 548 MB. Are the partition sizes reported by
> tablehistograms the decompressed size on disk?
>
> - John
>

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

<div dir=3D"ltr">Its the decompressed size of the partitions. Each sstable =
has stats component that contains histograms for the size and number of col=
umns in the partitions (among other things, can see with sstablemetadata to=
ol), tablehistograms merges it for each sstable and gives the results.<div>=
<br></div><div>Chris</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Feb 24, 2017 at 4:53 PM, John Sanda <span dir=3D"l=
tr">&lt;<a href=3D"mailto:john.sanda@gmail.com" target=3D"_blank">john.sand=
a@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr">I am working on some issues involving really big partitions. I ha=
ve been making extensive use of nodetool tablehistograms. What exactly is t=
he partition size being reported? I have a table for which the max value re=
ported is about 3.5 GB, but running du -h against the table data directory =
reports 548 MB. Are the partition sizes reported by tablehistograms the dec=
ompressed size on disk?<span class=3D"HOEnZb"><font color=3D"#888888"><div =
class=3D"m_-1070345346983379016gmail_signature" data-smartmail=3D"gmail_sig=
nature"><br>- John</div>
</font></span></div>
</blockquote></div><br></div>

--001a1137b2c030a94105494fe1ee--