You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/12/19 07:23:13 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-7658) stress connects to all nodes when it shouldn't

     [ https://issues.apache.org/jira/browse/CASSANDRA-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-7658:
------------------------------------
    Comment: was deleted

(was: I'm getting similar behavior from eea042b0b0abfb09f60b672c8930a924c5d7f25b where this was committed, so not sure this was ever fixed, or I'm somehow picking up a different driver version.)

> stress connects to all nodes when it shouldn't
> ----------------------------------------------
>
>                 Key: CASSANDRA-7658
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7658
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Brandon Williams
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 2.1.1
>
>         Attachments: 7658.txt, 7658.v2.txt
>
>
> If you tell stress -node 1,2 in cluster with more nodes, stress appears to do ring discovery and connect to them all anyway (checked via netstat.)  This led to the confusion on CASSANDRA-7567



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)