Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-21447

RedisClusterInvalidator subscriber does not recover properly on failure

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 7.10, 8.10, 9.1-SNAPSHOT
    • Fix Version/s: 7.10-HF22, 8.10-HF02, 9.1
    • Component/s: Redis

      Description

      In case of connection error there is a retry policy applied, by default trying to reconnect using an exponential delay.
      For the RedisClusterInvalidator subscriber once reconnected the delay is not reinitialized, so next failure will use the previous delay until the timeout is reached.

      Resolved by using a different retry policy on subscribers, the policy is try for ever with a constant backoff of 2s.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.