Uploaded image for project: 'DataStax Java Driver for Apache Cassandra'
  1. JAVA-1944

No mechanism exists for retrying ReadFailureException and WriteFailureException

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 3.6.0, DSE-1.7.0
    • Components: None
    • Labels:
      None
    • Sprint:

      Description

      As described here, when a READ_FAILURE or WRITE_FAILURE is returned from a coordinator, the driver currently throws this back to the user as ReadFailureException and WriteFailureException and skips RetryPolicy completely.

      We should consider enabling users to specify that these errors can be retried via RetryPolicy.onRequestError, although I believe in the general case, these should not be retried, so if we do make that change, we should add an exception in that method to not retry those by default.

        Attachments

          Activity

            People

            • Assignee:
              andrew.tolbert Andy Tolbert
              Reporter:
              andrew.tolbert Andy Tolbert
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: