[
https://issues.apache.org/jira/browse/CASSANDRA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795390#action_12795390
]
Jonathan Ellis commented on CASSANDRA-651:
------------------------------------------
I still think we should not rely on FD, or we will still hit this bug with
short-lived partitions (which do occur in the wild).
something like brandon's throwing an exception if not connected or awaiting
connection.
I'm still baffled that write() apparently doesn't throw when the connection
dies... Are we missing something there?
> cassandra 0.5 version throttles and sometimes kills traffic to a node if you
> restart it.
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-651
> URL: https://issues.apache.org/jira/browse/CASSANDRA-651
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.5
> Environment: latest in 0.5 branch
> Reporter: Ramzi Rabah
> Assignee: Gary Dusbabek
> Fix For: 0.5
>
> Attachments: 651-v2.patch, 651-v3.patch
>
>
> From the cassandra user message board:
> "I just recently upgraded to latest in 0.5 branch, and I am running
> into a serious issue. I have a cluster with 4 nodes, rackunaware
> strategy, and using my own tokens distributed evenly over the hash
> space. I am writing/reading equally to them at an equal rate of about
> 230 reads/writes per second(and cfstats shows that). The first 3 nodes
> are seeds, the last one isn't. When I start all the nodes together at
> the same time, they all receive equal amounts of reads/writes (about
> 230).
> When I bring node 4 down and bring it back up again, node 4's load
> fluctuates between the 230 it used to get to sometimes no traffic at
> all. The other 3 still have the same amount of traffic. And no errors
> what so ever seen in logs. "
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
