[ https://issues.apache.org/jira/browse/CASSANDRA-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016916#comment-16016916 ]
Paul Villacorta commented on CASSANDRA-13528: --------------------------------------------- I like the solution! It provides proper information of the snitch and eliminates the confusion. It would be nice also to have this patch on the forthcoming releases. Thanks! > nodetool describeclusters shows different snitch info as to what is > configured. > ------------------------------------------------------------------------------- > > Key: CASSANDRA-13528 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13528 > Project: Cassandra > Issue Type: Bug > Reporter: Paul Villacorta > Assignee: Lerh Chuan Low > Priority: Minor > Labels: lhf > Attachments: 13528-2.1.txt, 13528-trunk.txt, Screen Shot 2017-05-12 > at 14.15.04.png > > > I couldn't find any similar issue as this one so I'm creating one. > I noticed that doing nodetool describecluster shows a different Snitch > Information as to what is being set in the configuration file. > My setup is hosted in AWS and I am using Ec2Snitch. > cassandra@cassandra3$ nodetool describecluster > Cluster Information: > Name: testv3 > Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch > Partitioner: org.apache.cassandra.dht.Murmur3Partitioner > Schema versions: > fc6e8656-ee7a-341b-9782-b569d1fd1a51: > [10.0.3.61,10.0.3.62,10.0.3.63] > I checked via MX4J and it shows the same, I haven't verified tho using a > different Snitch and I am using 2.2.6 above and 3.0.X -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org