[
https://issues.apache.org/jira/browse/CASSANDRA-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935222#comment-13935222
]
Jonathan Ellis commented on CASSANDRA-6339:
-------------------------------------------
I'm pretty sure this doesn't meet the cost:benefit threshold to be worth a new
feature. We have tracing at a high level, and getendpoints + sstable2json at a
low level. These have been pretty successful at figuring out problems in my
experience, and I don't see the proposal as adding any new information on top.
> Provide mechanism for probing specific endpoints for a row key and/or column
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-6339
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6339
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Production
> Reporter: Ahmed Bashir
>
> In order to facilitate problem diagnosis, there should be a mechanism for
> retrieving row/column information from a specific node as opposed to having
> the said node request data from replicas with some CL and reconciling the
> data. This mechanism should also avoid read repair and so forth; just a
> simple way to probe an endpoint to see what it knows about a row and/or
> column(s).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
