[SERVER-32601] Add the ability to tag and close outgoing connections within a sharded cluster Created: 09/Jan/18 Updated: 30/Oct/23 Resolved: 15/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Mira Carey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Platforms 2018-02-26 | ||||||||
| Participants: | |||||||||
| Description |
|
One of the goals of the 3.8 upgrade/downgrade project is to close outgoing connections to servers running the last stable binary version on setFeatureCompatibilityVersion to the latest featureCompatibilityVersion, similarly to the way we close incoming connections when the featureCompatibilityVersion is bumped. In order to achieve this goal, the Storage team would like the Platforms team to add the ability to tag and close outgoing connections within a sharded cluster. |
| Comments |
| Comment by Githook User [ 15/Feb/18 ] |
|
Author: {'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'}Message: |