[SERVER-40616] awaitReplication should reset timeout when secondary makes progress Created: 12/Apr/19 Updated: 29/Oct/23 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc3, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Samyukta Lanka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Sprint: | Repl 2019-06-03, Repl 2019-06-17, Repl 2019-07-01 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Description |
|
ReplSetTest.awaitReplication() has a default timeout of 10 minutes. In certain suites/variants, this timeout is insufficient for secondaries to catch up. We should reset the timeout if the secondary makes progress, so that we don't time out if awaitReplication() would eventually succeed. This is preferable over just lengthening the timeout, so that if there is a deadlock, we don't wait unnecessarily. We could optionally have a hard timeout that applies even when secondaries are making progress, or we could rely on Evergreen test/task timeout. |
| Comments |
| Comment by Githook User [ 01/Jul/19 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: (cherry picked from commit f09aa80495bbd79997eaab415e7acdf8f29c18f9) |
| Comment by Githook User [ 24/Jun/19 ] |
|
Author: {'name': 'Samy Lanka', 'username': 'lankas', 'email': 'samy.lanka@mongodb.com'}Message: |