Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-7580

Investigate changes in PM-3613: Data Node Ingress Operation Queuing

    XMLWordPrintableJSON

Details

    • Icon: Investigation Investigation
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • No version
    • None
    • None
    • None
    • Developer Tools
    • Not Needed

    Description

      Original Downstream Change Summary

      New serverStatus metrics for the added queueing. New server parameters to configure max concurrency size for queues.

      Description of Linked Ticket

      Epic Summary

      Summary

      Implement a single queue at the data node ingress layer. This queue will be backed by a max concurrency ticketing system.

      Motivation

      Queuing at the data node ingress layer allows the customer to avoid data-bearing nodes receiving a number of operations that would induce overload symptoms. Backing the queue with a max concurrency ticketing system allows two levels of observability and constraint, having insight into both how many operations are currently running, and how many operations would like to begin running.

      Documentation

      Product Description
      Scope
      Technical Design
      Docs Update

      Attachments

        Activity

          People

            rhys.howell@mongodb.com Rhys Howell
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: