cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13695) ReadStage threads have no timeout
Date Tue, 22 Aug 2017 13:44:00 GMT


Joshua McKenzie updated CASSANDRA-13695:
    Component/s: Local Write-Read Paths

> ReadStage threads have no timeout
> ---------------------------------
>                 Key: CASSANDRA-13695
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Vladimir Yudovin
> Following this discussion: [High CPU after read timeout|]
> Currently ReadStage threads have no timeout and continue to run without limitation after
xxx_request_timeout_in_ms expired. Thus single bad request like SELECT ... ALLOW FILTERING
can paralyze the whole cluster for hours and even more.
> I guess that read request should include a kind *timeout *or *expired_at parameter* and
handling thread will check it and stop processing after expiration time.

This message was sent by Atlassian JIRA

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

View raw message