[CASSANDRA-14509] AsyncOneResponse uses the incorrect timeout

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Core
• Severity: Normal
• Assignee: Dinesh Joshi Assign to me
• Reporter: Dinesh Joshi

Authors

Dinesh Joshi

Reviewers

Marcus Eriksson

• Created: 08/Jun/18 23:37
• Updated: 15/May/20 08:00
• Resolved: 11/Jun/18 15:57

Description

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.

Issue Links

• is duplicated by: CASSANDRA-14510 Flaky uTest: RemoveTest.testRemoveHostId
• relates to: CASSANDRA-14514 StorageService::sendReplicationNotification has potential to end up in an infinite loop causing JVM to GC and die