[
https://issues.apache.org/jira/browse/CASSANDRA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908161#action_12908161
]
Jonathan Ellis commented on CASSANDRA-1490:
-------------------------------------------
we expose partitioner so that enterprising clients can route directly to the
"right" nodes for local reads rather than incurring the extra hop. snitch only
has the justification that it seems odd to have one in jmx and the other not.
> Expose partitioner and snitch via JMX
> -------------------------------------
>
> Key: CASSANDRA-1490
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1490
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Tools
> Reporter: paul cannon
> Priority: Minor
> Fix For: 0.7.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> It would be peachy keen if we could query a running cluster about the
> Partitioner and Snitch classes in use through some JMX call.
> Ex:
> org.apache.cassandra.service:type=StorageService : getClusterPartitioner()
> -> "org.apache.cassandra.dht.RandomPartitioner"
> org.apache.cassandra.service:type=StorageService : getClusterSnitch()
> -> "org.apache.cassandra.locator.SimpleSnitch"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
