Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14509

AsyncOneResponse uses the incorrect timeout

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 4.0
    • Component/s: Legacy/Core
    • Labels:
      None
    • Severity:
      Normal

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                djoshi3 Dinesh Joshi
                Reporter:
                djoshi3 Dinesh Joshi
                Authors:
                Dinesh Joshi
                Reviewers:
                Marcus Eriksson
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: