[
https://issues.apache.org/jira/browse/CASSANDRA-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams resolved CASSANDRA-6207.
-----------------------------------------
Resolution: Invalid
Fix Version/s: (was: 2.0.2)
Connection refused is pretty clear and not a hostname resolution problem.
Either the hostname resolution for whatever hostname you're specifying is wrong
on your system, or cassandra isn't configured to listen on the address it
resolves to.
> cassandra-stress does not honor host name using -d flag
> --------------------------------------------------------
>
> Key: CASSANDRA-6207
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6207
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: Linux
> Reporter: Rahul
> Priority: Blocker
>
> <cassandra_home>/apache-cassandra-2.0.1/tools/bin>./cassandra-stress -d
> <hostname>
> Above cmd throws exceptions like below
> Exception in thread "Thread-2" java.lang.RuntimeException:
> java.net.ConnectException: Connection refused
> at org.apache.cassandra.stress.Session.getClient(Session.java:763)
> at
> org.apache.cassandra.stress.Session.createKeySpaces(Session.java:692)
> at org.apache.cassandra.stress.StressAction.run(StressAction.java:64)
> Note: if host=localhost it works fine but if localhost is being replaced by
> machine name it start throwing java.net.ConnectException
--
This message was sent by Atlassian JIRA
(v6.1#6144)
