[COMPASS-7580] Investigate changes in PM-3613: Data Node Ingress Operation Queuing Created: 16/Jan/24  Updated: 23/Jan/24  Resolved: 17/Jan/24

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Rhys Howell
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Developer Tools
Documentation Changes: 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



 Comments   
Comment by PM Bot [ 23/Jan/24 ]

Fix Version updated for upstream PM-3613:
8.0 Targeted

Comment by Rhys Howell [ 17/Jan/24 ]

No devtools impact

Generated at Wed Feb 07 22:47:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.