[SERVER-30869] Use a failpoint to make replsets/initial_sync_rename_collection.js deterministic Created: 28/Aug/17 Updated: 30/Oct/23 Resolved: 27/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04 | ||||||||
| Participants: | |||||||||
| Description |
|
This test relies on creating 100 collections to take long enough for the primary to rename a collection before the secondary has completed initial sync. While this could only cause false negatives, and is unlikely to happen today, in the future that might change, causing us to miss test coverage without notice. |
| Comments |
| Comment by Githook User [ 27/Nov/17 ] |
|
Author: {'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}Message: |