[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   

	
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:32.363+0000 Program build/opt/mongo/db/range_deleter_test started with pid 9396.
2015-12-16 17:28:34 +0000	
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.571+0000 I -        [main] going to run suite: ImmediateDelete
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.571+0000 I -        [main] 	 going to run test: ShouldWaitCursor
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:34.572+0000 2015-12-16T17:28:34.572+0000 I SHARDING [thread1] waiting for open cursors before removing range [{ x: 0 }, { x: 10 }) in test.user, cursor ids: []
2015-12-16 17:28:36 +0000	
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:36.681+0000 2015-12-16T17:28:36.681+0000 I SHARDING [RangeDeleter] stopping range deleter worker
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:37.566+0000 2015-12-16T17:28:37.565+0000 I -        [main] FAIL: ShouldWaitCursor	Expected: stdx::future_status::ready == deleterFuture.wait_for(stdx::chrono::seconds(MAX_IMMEDIATE_DELETE_WAIT_SECS)) @src/mongo/db/range_deleter_test.cpp:204
[cpp_unit_test:range_deleter_test] 2015-12-16T17:28:37.566+0000 2015-12-16T17:28:37.565+0000 I -        [main] 	 going to run test: StopWhileWaitingCursor

Task:
https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_lsm_unittests_604d4f65e56b2a619cd71b0be8b41adcb03cd9ed_15_12_16_15_44_02
Logs:
https://logkeeper.mongodb.org/build/56719f1d9041306f24e09d12/test/56719f409041306f24e0aa19

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: SERVER-22066 Add more assertions to range_deleter_test
Branch: v3.2
https://github.com/mongodb/mongo/commit/59db3be4413f9a210a078a55d7ec98dc730b91c0

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: SERVER-22066 Add more assertions to range_deleter_test
Branch: master
https://github.com/mongodb/mongo/commit/b6d309a15215a9243f21eb33cc6bcb6fbca58e56

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.

Generated at Thu Feb 08 03:59:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.