cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14347) Read payload metrics
Date Mon, 24 Sep 2018 15:00:00 GMT


Aleksey Yeschenko updated CASSANDRA-14347:
    Fix Version/s:     (was: 4.0)

> Read payload metrics
> --------------------
>                 Key: CASSANDRA-14347
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sumanth Pasupuleti
>            Assignee: Sumanth Pasupuleti
>            Priority: Major
>             Fix For: 4.x
> We currently have MutationSizeHistogram that gives an idea of write payloads. This JIRA
is about adding similar capability to reads, which can benefit us with the following
>  * Histogram of payload sizes at Prepared Statement level
>  * Count of queries that meet vs do not meet SLO w.r.t. payload size
> We could also log queries that result in payload exceeding SLO. This can prove useful
in fire-fighting an incident, and can help resolve the issue since its easy to narrow down
to the specific culprit prepared statement.
> Read payload metrics could potentially be derived using network statistics, however,
it is difficult to isolate payloads due to reads, given that there could be a bunch of other
operations in C* that can amount to observed network traffic (like repairs, streaming, etc).

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message