[SERVER-55452] Write an integration test using mongo bridge to interrupt connection from mongos to primary Created: 23/Mar/21 Updated: 24/Mar/21 Resolved: 24/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Andrew Shuvalov (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
This is related to HELP ticket. This task is not exactly reproducing the problem, and may not help to resolve this ticket, however by itself it reproduces an important failure scenario. If we are lucky, it can uncover some problem related to HELP-22913 even though it's not the same failure. The idea is to make the primary invisible to mongos for some time, and then do the failover. We need to verify that mongos is capable to detect that primary is not functional and make the RSM to detect the new primary. |
| Comments |
| Comment by Andrew Shuvalov (Inactive) [ 24/Mar/21 ] |
|
Preempted by |