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

PriorityTicketHolder doesn't track operations that requeue after 500millis

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      It could be interesting to track the number of operations that time out at 500 milliseconds in a queue, wake up, and requeue for a ticket.

      Motivation: It could provide insight into what conditions cause the operations to get stuck in the queue & the side effects on latency and throughput when operations must wakeup to requeue.

      Example: Suppose 50th percentile latency is ~500 milliseconds, do we see higher tail latencies than expected? should we reconsider the 500 milliseconds timeout?

      Right now, we measure the number of cumulative number operations queued in the PriorityTicketHolder at the TicketHolderWithQueueingStats level. This means, it does not take into account the number of items that must requeue.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: