Use SessionMap for tracking per-db primary/replica usage - 2nd try
What does this MR do and why?
NOTE: this is a 2nd attempt of !170360 (merged) which was reverted due to a breakage in the regenerate-schema script.
Use SessionMap for tracking per-db primary/replica usage
This MR releases the change introduced earlier by removing the feature flag. Primary/replica usage of each connection is now tracked separately.
Changelog: other MR: !168642 (merged)
References
Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.