cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-651) cassandra 0.5 version throttles and sometimes kills traffic to a node if you restart it.
Date Tue, 29 Dec 2009 18:55:29 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795103#action_12795103
] 

Jonathan Ellis edited comment on CASSANDRA-651 at 12/29/09 6:55 PM:
--------------------------------------------------------------------

relying on FD to notice is not going to work, though, since FD is not instantaneous (and cannot
be made so).  [edit: that is, a node could die and come back, or be partitioned and be available
again, quickly enough that FD does not notice but old connections are still invalid.] 

can we have it attempt to reconnect when it encounters an error sending instead?

      was (Author: jbellis):
    relying on FD to notice is not going to work, though, since FD is not instantaneous (and
cannot be made so).  can we have it attempt to reconnect when it encounters an error sending
instead?
  
> 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.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.


Mime
View raw message