y, July 7, 2010 11:50am
To: user@cassandra.apache.org
Subject: Re: Cluster performance degrades if any single node is slow
On Wed, Jul 7, 2010 at 11:33 AM, Jonathan Ellis wrote:
> Having a few requests time out while the service detects badness is
> typical in this kind of system. I
On Wed, Jul 7, 2010 at 11:50 AM, Mason Hale wrote:
> I'm curious of what performance benefit is actually being gained from this
> optimization.
It's really pretty easy to saturate gigabit ethernet with a Cassandra
cluster. Mulitplying traffic by roughly RF is definitely a lose.
> Sorry to keep
On Wed, Jul 7, 2010 at 11:33 AM, Jonathan Ellis wrote:
> Having a few requests time out while the service detects badness is
> typical in this kind of system. I don't think writing a completely
> separate StorageProxy + supporting classes to allow avoiding this in
> exchange for RF times the net
Having a few requests time out while the service detects badness is
typical in this kind of system. I don't think writing a completely
separate StorageProxy + supporting classes to allow avoiding this in
exchange for RF times the network bandwidth is a good idea.
On Wed, Jul 7, 2010 at 11:23 AM,
We've been experiencing some cluster-wide performance issues if any single
node in the cluster is performing poorly. For example this occurs if
compaction is running on any node in the cluster, or if a new node is being
bootstrapped.
We believe the root cause of this issue is a performance optimiz
