You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2024/06/07 18:45:00 UTC

[jira] [Updated] (CASSANDRA-19693) Relax slow_query_log_timeout for MultiNodeSAITest

     [ https://issues.apache.org/jira/browse/CASSANDRA-19693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Caleb Rackliffe updated CASSANDRA-19693:
----------------------------------------
    Change Category: Performance
         Complexity: Low Hanging Fruit
      Fix Version/s: 5.x
             Status: Open  (was: Triage Needed)

> Relax slow_query_log_timeout for MultiNodeSAITest
> -------------------------------------------------
>
>                 Key: CASSANDRA-19693
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19693
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/SAI, Test/fuzz
>            Reporter: Caleb Rackliffe
>            Assignee: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 5.x
>
>
> To stress the paging subsystem, we intentionally use a comically low fetch size in {{{}MultiNodeSAITest{}}}. This can lead to some very slow queries when we get matches into the hundreds of rows. It looks like CASSANDRA-19534 has gotten a little more aggressive about how the slow query timeout is triggered, and there’s a lot of noise around this in the logs, even in local runs. I think bumping the default slow query timeout and perhaps the native protocol timeout a bit should clear this up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org