ABUSE
YA NO QUIERO MAS MAILS SOY DE MEXICO
De: Nikolai Grigoriev [mailto:ngrigor...@gmail.com]
Enviado el: sábado, 22 de noviembre de 2014 07:13 p. m.
Para: user@cassandra.apache.org
Asunto: Re: Compaction Strategy guidance
Importancia: Alta
Stephane,
As everything good, LCS comes at
Stephane,
As everything good, LCS comes at certain price.
LCS will put most load on you I/O system (if you use spindles - you may
need to be careful about that) and on CPU. Also LCS (by default) may fall
back to STCS if it is falling behind (which is very possible with heavy
writing activity) and
Hi there,
use case:
- Heavy write app, few reads.
- Lots of updates of rows / columns.
- Current performance is fine, for both writes and reads..
- Currently using SizedCompactionStrategy
We're trying to limit the amount of storage used during compaction. Should
we switch to LeveledCompactionStr
Hi Dmitri,
I have not used the CPP driver, but maybe you have forgotten set the equivalent
of the Iava driver's fetchsize to something sensible?
Just an idea,
Jens
—
Sent from Mailbox
On Sun, Nov 16, 2014 at 6:09 PM, Dmitri Dmitrienko
wrote:
> Hi,
> I have a very simple table in cassan
Hello,
I posted a similar issue the other day. We wound up not nuking the data dir
and simply deleting the system keyspace from the data dir and then
restarted the node. This actually worked and caused our never-ending join
process to complete and the node is now a part of the cluster.
Stan Lemon
