Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 13 Sep 2014 15:37:34 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12731098.1406823009000.27529.1410622654306@Atlassian.JIRA>
In-Reply-To: <JIRA.12731098.1406823009000@Atlassian.JIRA>
References: <JIRA.12731098.1406823009000@Atlassian.JIRA>
 <JIRA.12731098.1406823009805@arcas>
Subject: [jira] [Updated] (CASSANDRA-7658) stress connects to all nodes when
 it shouldn't
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedict updated CASSANDRA-7658:
--------------------------------
    Attachment: 7658.v2.txt

> 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)