Repository navigation
Add business QoS configuration for URMA - #3712
Spicy-cream wants to merge 37 commits into
Conversation
|
Thanks for the review. I’ll move the mock SEND completion fix and its CI wiring to #3708, then rebase this PR after #3708 lands so the diff contains only the QoS changes. The use case is a single process with both latency-sensitive RPCs and bulk traffic. Those channels need different outgoing priorities, while channels with no explicit setting can inherit the process default. I’ll document the device limits and resource cost. The selected device and path expose up to 16 effective priority/SL mappings, and unsupported settings fail initialization with the available mappings in the diagnostic. Jetty usage scales with live URMA connections and the prepared pool. Connections with non-default priorities allocate Jettys on demand. |
(cherry picked from commit 351935a)
What problem does this PR solve?
A process can serve latency-sensitive RPCs alongside bulk traffic. Channel and server options let each workload set its outgoing priority, with the process default available for other traffic.
This PR depends on PR3708. The source branch includes its recovery changes; merge PR3708 first.
What is changed and the side effects?
The selected path exposes up to 16 priority/SL mappings per device. Live URMA connections each use a Jetty at each end. Connections with the default priority and compatible queues can use a prepared Jetty. Other connections allocate Jettys on demand. The channel signature includes the configured priority and SL, so equivalent settings can use separate connections. Existing v2/v3 wire formats remain compatible.
Validation
Design discussion: URMA runtime recovery and business QoS configuration.
Check List