cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9205) Allow per statement time outs or request cancel method
Date Sun, 05 Feb 2017 16:34:42 GMT


Aleksey Yeschenko updated CASSANDRA-9205:
    Fix Version/s:     (was: 3.x)

> Allow per statement time outs or request cancel method
> ------------------------------------------------------
>                 Key: CASSANDRA-9205
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Vishy Kasar
> Cassandra lets user specify time outs for various operations globally in yaml. It would
be great if we could set different timeouts for CQL statements in different contexts, rather
than just having a global  timeouts in yaml. We have client requests that need to time out
in a short duration vs some maintenance requests that we know take long. The only choice we
have now is to set the server time out to the highest needed. 
> User can certainly do session.executeAsync on the client side and wait for certain time
on the returned future. However when user cancels the future on time out, nothing is done
on the server side. We have seen cases where cassandra replicas were going over thousands
of tombstones and causing OOMs way after client timed out. 
> This can be implemented either by passing the time out along with query to server or
by providing a cancel method similar to
> It is understood that server may not be able to timeout/cancel the requests in all cases.
So this is a request to server to do it's best effort to timeout/cancel.

This message was sent by Atlassian JIRA

View raw message