[SERVER-38513] Implement disconnection behavior for legacy messages Created: 10/Dec/18 Updated: 29/Oct/23 Resolved: 07/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Gregory McKeon (Inactive) | Assignee: | Matthew Russotto |
| 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: | Repl 2018-12-17, Repl 2019-01-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Testing should include:
|
| Comments |
| Comment by Matthew Russotto [ 07/Jan/19 ] |
|
It appears the server's response to a write on a secondary is not currently documented, so no change is needed. |
| Comment by Githook User [ 07/Jan/19 ] |
|
Author: {'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}Message: |