Thanks for the reply Aaron.
I was thinking along the same lines as well.. as its only specific nodes
that were showing excessive writes.. during the heavy read operations.
We will be performing the same exercise again today.. where can I see within
the JMX info if a specific node is performing a
Just to clarify, the data that we're loading SSTables from (v1.0.3) doesn't
have compression enabled on any of the CF's.
So in theory the compression should occur on the receiving end (v1.1.1) as
we're going from uncompressed data to compressed data.
So I'm not sure if the bug you mention is cau
Thanks Sylvain.
I had a look at a node where we streamed data to and I do indeed see the
"..-CompressionInfo.db" files..
However, prior to running the "upgradesstables" command, the total size of
all the SSTables was 27GB and afterwards its 12GB.
So even though the CompressionInfo files were the
Sure, before I create a ticket, is there a way I can confirm that the
sstables are indeed not compressed other than running the "rebuildsstables"
nodetool command (and observing the live size go down)?
Thanks.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2
