Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "FAQ" page has been changed by EricEvans. The comment on this change is: document effects of poorly configured name resolution on jmx apps. http://wiki.apache.org/cassandra/FAQ?action=diff&rev1=50&rev2=51 -------------------------------------------------- * [[#range_ghosts|Why do deleted keys show up during range scans?]] * [[#change_replication|Can I change the ReplicationFactor on a live cluster?]] * [[#large_file_and_blob_storage|Can I store large files or BLOBs in Cassandra?]] + * [[#jmx_localhost_refused"|Nodetool says "Connection refused to host: 127.0.1.1", for any remote host. What gives?]] <<Anchor(cant_listen_on_ip_any)>> @@ -208, +209 @@ Currently Cassandra isn't optimized specifically for large file or BLOB storage, however there are ways to work around this. * Please refer to the notes in the Cassandra limitations section for more information: [[CassandraLimitations|Cassandra Limitations]] + <<Anchor(jmx_localhost_refused)>> + == Nodetool says "Connection refused to host: 127.0.1.1", for any remote host. What gives? == + + Nodetool relies on JMX, which in turn relies on RMI, which in turn sets up it's own listeners and connectors as needed on each end of the exchange. Normally all of this happens behind the scenes transparently, but incorrect name resolution for either the host connecting, or the one being connected to, can result in crossed wires and confusing exceptions. + + If you are not using DNS, then make sure that your `/etc/hosts` files are accurate on both ends. If that fails try passing the `-Djava.rmi.server.hostname=$IP` option to the JVM at startup (where `$IP` is the address of the interface you can reach from the remote machine). +
