cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14509) AsyncOneResponse uses the incorrect timeout
Date Mon, 11 Jun 2018 15:58:00 GMT

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

Marcus Eriksson updated CASSANDRA-14509:
----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.0
           Status: Resolved  (was: Patch Available)

and committed as {{6da5fb56c8e0777843e88359a45a461a9f9eb639}} without the test.runners change
- if that is a problem we should probably fix that in a separate ticket, thanks!

> AsyncOneResponse uses the incorrect timeout
> -------------------------------------------
>
>                 Key: CASSANDRA-14509
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14509
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Dinesh Joshi
>            Assignee: Dinesh Joshi
>            Priority: Major
>             Fix For: 4.0
>
>
> {{AsyncOneResponse}} has a bug where it uses the initial timeout value instead of the
adjustedTimeout. Combined with passing in the wrong {{TimeUnit}}, it leads to a shorter timeout
than expected. This can have unintended consequences for example, in {{StorageService::sendReplicationNotification}}
instead of waiting 10 seconds ({{request_timeout_in_ms}}), we wait for {{10000}} Nano Seconds.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message