We have a separate RPC connection class for rangefeeds, but it's disabled by default via kv.rangefeed.use_dedicated_connection_class.enabled.
Rangefeeds can be high-volume during e.g. initial/catchup-scans, and have a high restart cost if they e.g. hit NetworkTimeout. We should consider enabling this class by default, plumbing it through not only for the DistSender connections but also the DistSQL flow, and use a higher network timeout since they're not as sensitive to availability following outages.
Jira issue: CRDB-30735
Epic CRDB-32846
We have a separate RPC connection class for rangefeeds, but it's disabled by default via
kv.rangefeed.use_dedicated_connection_class.enabled.Rangefeeds can be high-volume during e.g. initial/catchup-scans, and have a high restart cost if they e.g. hit
NetworkTimeout. We should consider enabling this class by default, plumbing it through not only for the DistSender connections but also the DistSQL flow, and use a higher network timeout since they're not as sensitive to availability following outages.Jira issue: CRDB-30735
Epic CRDB-32846