Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84421

Unexpected flow control engaged during benchmark

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL
    • Hide

      Cannot reproduce

      Show
      Cannot reproduce

      During a benchmark, we found there is many slow log waiting for flow control tickets, we decompress the diagnostic metric data, and find flow control engaged

      But we don't find any majority committed lay in corresponding point

      According to the configuration of flow control, only replication lay greater than 5s, can flow control engaged

       

        1. image-2023-12-27-17-00-25-921.png
          793 kB
          jum zhang
        2. image-2023-12-27-17-02-05-514.png
          183 kB
          jum zhang
        3. image-2023-12-27-17-02-24-056.png
          194 kB
          jum zhang
        4. image-2023-12-27-17-02-40-532.png
          194 kB
          jum zhang
        5. image-2023-12-27-17-04-46-702.png
          214 kB
          jum zhang
        6. metrics.2023-12-26T16-10-09Z-00000
          9.77 MB
          jum zhang
        7. image-2023-12-28-19-46-51-844.png
          171 kB
          jum zhang
        8. Screenshot 2024-01-08 at 12.33.31 PM.png
          206 kB
          Edwin Zhou

            Assignee:
            edwin.zhou@mongodb.com Edwin Zhou
            Reporter:
            zhangwenjumlovercl@gmail.com jum zhang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: