[SERVER-24284] RangeDeleter hangs for 10+ hours Created: 25/May/16  Updated: 30/May/16  Resolved: 27/May/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: xihui he Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

From the below log, it shows the RangeDeleter is blocked by the same cursor ids for 10+ hours. However from currentOp I can't find any long run operation. Is there any way to kill this cursors?

2016-05-25T18:09:13.585+0800 I SHARDING [RangeDeleter] waiting for open cursors before removing range [{ _id: 6231868376436703237 }, { _id: 6232234393914572805 }) in media.media_region_v3, elapsed secs: 76568, cursor ids: [103122690435, 103234458201, 103344882313, 103466762560, 103486678846, 104529433592, 104653619739, 105278680037, 105661554876, 105896835551, 105976246882, 106650340093]
2016-05-25T18:09:13.586+0800 I SHARDING [RangeDeleter] waiting for open cursors before removing range [{ _id: 6246632721800495110 }, { _id: 6246637544973271046 }) in media.media_region_v3, elapsed secs: 26988, cursor ids: [103122690435, 103234458201, 103344882313, 103466762560, 103486678846, 104529433592, 104653619739, 105278680037, 105661554876, 105896835551, 105976246882, 106650340093]
2016-05-25T18:09:13.788+0800 I SHARDING [RangeDeleter] waiting for open cursors before removing range [{ _id: 6239781522933547014 }, { _id: 6239917119236997125 }) in media.media_region_v3, elapsed secs: 63893, cursor ids: [103122690435, 103234458201, 103344882313, 103466762560, 103486678846, 104529433592, 104653619739, 105278680037, 105661554876, 105896835551, 105976246882, 106650340093]



 Comments   
Comment by xihui he [ 30/May/16 ]

ramon.fernandez It's expected that the notimeout cursor still open even all the mongos are restarted?

Comment by Ramon Fernandez Marina [ 27/May/16 ]

bydsky, you may want to consider using a default cursor timeout (SERVER-8188) or update your application if possible to have timeouts for cursors.

Since this is expected behavior I'm going to close this ticket. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Comment by xihui he [ 26/May/16 ]

We guess it may be related to https://github.com/MongoEngine/mongoengine/pull/1304. MongoEngine uses noCursorTimeout by default.

Comment by xihui he [ 25/May/16 ]

I restarted all mongos and it doesn't work.

Comment by xihui he [ 25/May/16 ]

version 3.2.5
engine wiredTiger

Generated at Thu Feb 08 04:05:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.