Uploaded image for project: 'Ratis'
  1. Ratis
  2. RATIS-574

Client should not use configured sleep interval in RetryPolicy when it gets NotLeaderException

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.4.0
    • client
    • None

    Description

      While doing performance tests with Ozone, it was observed that the client always waits for retry timeout when a NotLeaderException is logged. This bears a performance penalty for the client who cannot try the next Ratis server in the ring.

      Attachments

        1. RATIS-574.01.patch
          13 kB
          Siddharth Wagle
        2. RATIS-574.04.patch
          10 kB
          Siddharth Wagle
        3. RATIS-574.05.patch
          11 kB
          Siddharth Wagle
        4. RATIS-574.07.patch
          9 kB
          Siddharth Wagle
        5. RATIS-574.08.patch
          9 kB
          Siddharth Wagle

        Issue Links

          Activity

            People

              swagle Siddharth Wagle
              avijayan Aravindan Vijayan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m