[SERVER-22066] range_deleter_test:ImmediateDelete is flaky Created: 16/Dec/15 Updated: 21/Nov/16 Resolved: 06/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.3, 3.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Adam Midvidy | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Sharding E (01/08/16) |
| Participants: |
| Description |
Task: Assigning to acm for triage since he was last to touch this file. |
| Comments |
| Comment by Githook User [ 14/Jan/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 06/Jan/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Kaloian Manassiev [ 05/Jan/16 ] |
|
This test specifically tests that the range deleter thread activates within 2 seconds of certain condition taking effect, so there is no way to add an explicit signal. I am going to tighten up the assertions a bit and bump the wait interval to 3 seconds, but otherwise leave it as is. |
| Comment by Andrew Morrow (Inactive) [ 05/Jan/16 ] |
|
adam.midvidy - I'm assigning this to kaloian.manassiev. While I was the last to touch the file, my changes only changed the mechanism by which we waited for the range_deleter. It worked properly for several months, so my guess is that either something else changed, or that the wait is insufficient or needs some more explicit signal of completion. I think sharding team should own this one. |