Uploaded image for project: 'Bookkeeper'
  1. Bookkeeper
  2. BOOKKEEPER-602

we should have request timeouts rather than channel timeout in PerChannelBookieClient

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.2.0, 4.2.1
    • Fix Version/s: 4.3.0, 4.2.3
    • Component/s: bookkeeper-client
    • Labels:
      None

      Description

      currently we only have readTimeout in netty channel, it timeouts only when there is no activities in that channel, but it can't track timeouts of individual requests. if a channel continues having read entry activities, it might shadow a slow add entry response, which is bad impacting add latency.

        Attachments

        1. BOOKKEEPER-602.diff
          26 kB
          Sijie Guo
        2. BOOKKEEPER-602.diff
          27 kB
          Sijie Guo
        3. BOOKKEEPER-602_branch42.diff
          22 kB
          Sijie Guo
        4. 0001-BOOKKEEPER-602-we-should-have-request-timeouts-rathe.patch
          24 kB
          Ivan Kelly

          Activity

            People

            • Assignee:
              i0exception Aniruddha
              Reporter:
              hustlmsp Sijie Guo
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: