You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Dinesh Joshi (JIRA)" <ji...@apache.org> on 2018/06/08 23:43:00 UTC

[jira] [Updated] (CASSANDRA-14509) AsyncOneResponse uses the incorrect timeout

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

Dinesh Joshi updated CASSANDRA-14509:
-------------------------------------
    Fix Version/s: 4.x
           Status: Patch Available  (was: Open)

||14509||
|[branch|https://github.com/dineshjoshi/cassandra/tree/trunk-14509]|
|[utests &amp; dtests|https://circleci.com/gh/dineshjoshi/workflows/cassandra/tree/trunk-14509]|
||

> 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.x
>
>
> {{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