cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <>
Subject [jira] [Reopened] (CASSANDRA-7658) stress connects to all nodes when it shouldn't
Date Fri, 19 Dec 2014 05:38:14 GMT


Ryan McGuire reopened CASSANDRA-7658:

This has regressed, there seems to be two issues here:

1) the nodes it's contacting is not restricted to those specified on the command line.
2) the nodes it is contacting is not contacting the broadcast_address, but rather the listen_address.
This fails in a multi-dc EC2 cluster for instance where the listen_address is a private IP.

Here's a log from a multi-dc cluster setup on EC2. I'm running from DC1, and only specifying
another node in DC1. It shows that it's trying to contact nodes in DC2 that a) are not on
in the stress command line and b) is not using the public broadcast IP

$ ~/fab/stress/cassandra-2.1/tools/bin/cassandra-stress write n=19000000 -schema replication\(strategy=NetworkTopologyStrategy,factor=2\)
Unable to create stress keyspace: Error constructing replication strategy class
Warming up WRITE with 50000 iterations...
INFO  04:51:32 Using data-center name 'DC2' for DCAwareRoundRobinPolicy (if this is incorrect,
please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor)
Connected to cluster: cstar_perf 1EEJMMEZHQ
Datatacenter: DC2; Host: /; Rack: r1
Datatacenter: DC2; Host: /; Rack: r1
Datatacenter: DC2; Host: /; Rack: r1
Datatacenter: DC1; Host:; Rack:
Datatacenter: DC1; Host: /; Rack: r1
INFO  04:51:32 New Cassandra host / added
INFO  04:51:32 New Cassandra host / added
ERROR 04:51:37 Error creating pool to /
com.datastax.driver.core.TransportException: [/] Cannot connect
        at com.datastax.driver.core.Connection.<init>( ~[cassandra-driver-core-2.0.5.jar:na]
        at com.datastax.driver.core.PooledConnection.<init>(
        at com.datastax.driver.core.Connection$ ~[cassandra-driver-core-2.0.5.jar:na]
        at com.datastax.driver.core.HostConnectionPool.<init>(
        at com.datastax.driver.core.SessionManager.replacePool( ~[cassandra-driver-core-2.0.5.jar:na]
        at com.datastax.driver.core.SessionManager.access$400( ~[cassandra-driver-core-2.0.5.jar:na]
        at com.datastax.driver.core.SessionManager$ [cassandra-driver-core-2.0.5.jar:na]
        at com.datastax.driver.core.SessionManager$ [cassandra-driver-core-2.0.5.jar:na]
        at [na:1.7.0_45]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
        at [na:1.7.0_45]
Caused by: connection timed out: /
        at ~[netty-3.9.0.Final.jar:na]
        ... 3 common frames omitted

> stress connects to all nodes when it shouldn't
> ----------------------------------------------
>                 Key: CASSANDRA-7658
>                 URL:
>             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

View raw message