[
https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022907#comment-13022907
]
paul cannon commented on CASSANDRA-2238:
----------------------------------------
bq. Can you elaborate on why that's a bad idea?
Cause it seems like a pretty arbitrary information source. I've seen remarkably
few production environments that provided actual, resolvable, useful,
consistent IP->name lookups between internal addresses. In most cases, when a
reverse lookup name is available, it will be a mostly-useless restatement of
the IP (like "c124-54-18-41.random.cloudsite.com"), or it will have a good
change of being different depending on the request's origin node. And even when
a consistent answer is available, nodetool won't know if it is supposed to get
it via PTR request through DNS, or through a different OS administrative
interface (like /etc/hosts, getent, NSS), or by something entirely different.
When a user has a need for this, it might be more straightforward for them to
use a dumb awk script to replace the first field of nodetool output with a
name, translated according to their own site procedures.
> Allow nodetool to print out hostnames given an option
> -----------------------------------------------------
>
> Key: CASSANDRA-2238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2238
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Joaquin Casares
> Assignee: paul cannon
> Priority: Trivial
> Fix For: 0.8.1
>
>
> Give nodetool the option of either displaying IPs or hostnames for the nodes
> in a ring.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
