Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-3961

Cold Standby revisit timeout setup

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.16, 1.3.15, 1.4
    • Component/s: tarmk-standby
    • Labels:
      None

      Description

      The timeout settings are too large and inefficient, making all the tests very slow. On top of this the current timeout if being enforced in 2 places, which turns out it doesn't play too well with the sync mechanism:

      • one is via the ReadTimeoutHandler in the StandbyClient
      • second is in the SegmentLoaderHandler
        as it turns out the first one is a global kill switch, and it will fail any transaction larger than the set value (all of the sync cycle), which is not what I meant to do with it, so I'll remove it and only leave the second one, which is a timeout per request (segment or binary).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                stillalex Alex Deparvu
                Reporter:
                stillalex Alex Deparvu
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: