[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995272#comment-13995272 ] Yasuharu Goto commented on CASSANDRA-2238: -- OK, I opened a new tickeet CASSANDRA-7210. Thank you. > 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: Daneel S. Yaitskov >Priority: Trivial > Fix For: 1.2.14, 2.0.5 > > Attachments: trunk-2238.txt > > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995230#comment-13995230 ] Jonathan Ellis commented on CASSANDRA-2238: --- Can you open a new ticket, since it will go into a different release than the original? > 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: Daneel S. Yaitskov >Priority: Trivial > Fix For: 1.2.14, 2.0.5 > > Attachments: trunk-2238.txt > > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848435#comment-13848435 ] Daneel S. Yaitskov commented on CASSANDRA-2238: --- I've cherry-picked this commit into 1.2 trunk. You can find it here https://github.com/yaitskov/cassandra/tree/nodetool-status-resolve-ip-support-for-1.2 > 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 >Priority: Trivial > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847688#comment-13847688 ] Daneel S. Yaitskov commented on CASSANDRA-2238: --- Okay. I'll do rebasing to get for 1.2 too. > 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 >Priority: Trivial > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847675#comment-13847675 ] Brandon Williams commented on CASSANDRA-2238: - LGTM but I don't see any reason to only put this in trunk (2.1). [~yaitskov] mind rebasing for 1.2? > 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 >Priority: Trivial > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841103#comment-13841103 ] Daneel Yaitskov commented on CASSANDRA-2238: pull request git clone https://github.com/yaitskov/cassandra.git branch nodetool-status-resolve-ip-support > 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 >Priority: Trivial > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840288#comment-13840288 ] Daneel Yaitskov commented on CASSANDRA-2238: I want to have an option in nodetool to enable reverse IP resolving. It's very inconvenient. My cluster is maintained by chef. So I recall about IPs at VM creation process only. Look at that. I see tens of IPs and one node failed. I had to remember bunch of numbers each time to enter them in neighbor console. IPv6 is just around the corner. What could you do with that?! Networking toolkit route makes reverse resolving by default. > 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 >Priority: Trivial > > Give nodetool the option of either displaying IPs or hostnames for the nodes > in a ring. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025903#comment-13025903 ] Brandon Williams commented on CASSANDRA-2238: - I think doing a reverse lookup is fine, as long as it requires a flag and is not the default. Personally, my clusters always have a synced /etc/hosts so a lookup isn't a problem, and would be terribly convenient compared to using a script or memorizing the IPs. > 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 >Priority: Trivial > > 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
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023148#comment-13023148 ] Sylvain Lebresne commented on CASSANDRA-2238: - I would argue than calling InetAddress.getHostName() would be a really trivial to use and would in most cases 'do the right thing' (provided you have not some weird ass configuration). It will be useful in environments where a reverse DNS lookup do the right thing (imho, any non cloudy environment "should" - I know the cloud is the new cool thing around, but let's not restrict us to that arbitrarily) and the hostnames are what people are used to. I know at least one such environment where I would have been happy to have that option. Granted, this won't always be perfect, but if this is an option it's OK if it is only useful for 10% of users. And granted too, it is easy enough to write a awk or shell script but I think having the option directly will give a nicer sense of polish to nodetool (and thus Cassandra). If as an admin I had taken time and love to configure my environment correctly, I would be pissed to have to write a script because Cassandra "is too dumb to do a reverse DNS". Moreover, we trade 5 lines of changes on our side against all user that wants it writing scripts (and you know Cassandra will soon rule the world, so that will be a lot of users). Anyway, just saying. It's no big deal and I don't care so much, but I do think we should try to strive making Cassandra as easy on the user as possible, even in the details. And if I've convinced you, know that I'll be happy to write the 5 lines patch. > 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 >Priority: Trivial > > 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
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ 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
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[ https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022610#comment-13022610 ] Jonathan Ellis commented on CASSANDRA-2238: --- bq. If instead this ticket is asking for reverse DNS lookups or something, then I'm -1 on the whole thing. Can you elaborate on why that's a bad idea? > 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
[jira] [Commented] (CASSANDRA-2238) Allow nodetool to print out hostnames given an option
[
https://issues.apache.org/jira/browse/CASSANDRA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022608#comment-13022608
]
paul cannon commented on CASSANDRA-2238:
It might be nontrivial- it depends on what we define as the hostname for a
node: the node's own OS {{hostname}} output, or some other lookup (DNS, NSS,
etc) of each node IP from the system running nodetool? The former makes more
sense, but the only way I could identify to accomplish it, last time I tried,
was to query the {{Name}} attribute of {{java.lang:type=Runtime}}, and depend
on it always containing the local hostname after the @ sign. I have no idea
whether that's a valid thing to depend on, and it seems a little bit
excessively ghetto for something like nodetool.
The right solution would probably be adding a jmx attribute exposing the "real"
node name.
If instead this ticket is asking for reverse DNS lookups or something, then I'm
-1 on the whole thing.
> 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
