thank you let me review.
On Fri, Oct 26, 2018 at 3:35 PM Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> Here's the metrics you want:
> http://cassandra.apache.org/doc/latest/operating/metrics.html#table-metrics
>
> The best practice is to run fewer bigger tables. If it's a lot of ta
Here's the metrics you want:
http://cassandra.apache.org/doc/latest/operating/metrics.html#table-metrics
The best practice is to run fewer bigger tables. If it's a lot of tables
you're likely out of luck aside from throwing more RAM at the problem.
All the best,
Sebastián Estévez | Vanguard So
anyone has any idea on this?
On Thu, Oct 25, 2018 at 11:35 AM Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> Hello,
>
> I am running into a situation where huge schema (# of CF) causing OOM
> issues to the heap. is there a way to measure how much size each column
> family uses in the
Hello,
I am running into a situation where huge schema (# of CF) causing OOM
issues to the heap. is there a way to measure how much size each column
family uses in the heap?
wn CFS on the fly or 1 per customer
designs.
When the wrinkles come out of 1.1 and up upgrade the schema size
should shrink down.
On Fri, May 25, 2012 at 6:25 AM, Sasha Yanushkevich wrote:
> Hi All,
>
> I have a question about schema cleaning in cassandra.
>
> I use cassandra versi
Hi All,
I have a question about schema cleaning in cassandra.
I use cassandra version 1.0.9. I have 5 keyspaces and about 1500 column
family per keyspace. After dynamically creating and deleting CF my schema's
sstables size were very high. For example size of Migrations was 45 GB and
Schema sst