[
https://issues.apache.org/jira/browse/CASSANDRA-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654761#comment-13654761
]
Peter Bailis commented on CASSANDRA-5455:
-----------------------------------------
I don't believe that the StorageProxy tracks the latencies according to the
same granularity. For example, the PBS latency tracking will record both how
long it took for the request to reach a remote replica and be processed as well
as how long the return trip takes.
That said, it shouldn't be too difficult to either 1.) simply expose the
recorded latencies via an optional module providing a "finer granularity
tracing" interface via JMX [thereby removing all actual prediction code but
keeping the logging in place for folks who might want this] or 2.) modifying
StorageProxy to log these latencies in addition to the coarser granularity
measurements it already takes.
I can provide assistance with either.
> Remove PBSPredictor
> -------------------
>
> Key: CASSANDRA-5455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5455
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 2.0
>
> Attachments: 5455.txt
>
>
> It was a fun experiment, but it's unmaintained and the bar to understanding
> what is going on is high. Case in point: PBSTest has been failing
> intermittently for some time now, possibly even since it was created. Or
> possibly not and it was a regression from a refactoring we did. Who knows?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
