Thanks! I'm actually on vacation now, so I hope to look into this next week.
On Mon, Jun 6, 2011 at 10:25 PM, aaron morton wrote:
> You should consider upgrading to 0.7.6 to get a fix to Gossip. Earlier 0.7
> releases were prone to marking nodes up and down when they should not have
> been. See
You should consider upgrading to 0.7.6 to get a fix to Gossip. Earlier 0.7
releases were prone to marking nodes up and down when they should not have
been. See https://github.com/apache/cassandra/blob/cassandra-0.7/CHANGES.txt#L22
Are the TimedOutExceptions to the client for read or write reques
Version 0.7.3.
Yes, I am talking about minor compactions. I have three nodes, RF=3.
3G data (before replication). Not many users (yet). It seems like 3
nodes should be plenty. But when all 3 nodes are compacting, I
sometimes get timeouts on the client, and I see in my logs that each
one is full of
Are you talking about minor (automatic) compactions ? Can you provide some more
information on what's happening to make the node unusable and what version you
are using? It's not lightweight process, but it should not hurt the node that
badly. It is considered an online operation.
Delaying co
Is there some deep architectural reason why compaction can't be
replication-aware?
What I mean is, if one node is doing compaction, its replicas
shouldn't be doing compaction at the same time. Or, at least a quorum
of nodes should be available at all times.
For example, if RF=3, and one node is d
