[SERVER-51157] Improve stability of TagsTest in v3.6 Created: 25/Sep/20 Updated: 06/Dec/22 Resolved: 28/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.6.20 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 15 | ||||||||||||
| Description |
|
The TagsTest relies on priority takeover to have certain nodes take over as primary. This makes the initial startup and configuration phase unstable, since it can cause an existing, lower priority primary to step down while another node is syncing from it. This was fixed by The BF on v3.6 doesn't happen often and this is probably low priority since v3.6 EOL is soon. |
| Comments |
| Comment by Judah Schvimer [ 25/Sep/20 ] |
|
I think marking the BF as trivial and closing this Won't Fix as you mention is reasonable. |