[SERVER-26755] Collection chunk loading is aborted entirely if fetching all the chunks takes more than 30 seconds Created: 24/Oct/16  Updated: 03/Feb/22  Resolved: 19/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.17, 4.2.4, 4.0.17
Fix Version/s: 4.7.0, 4.2.19, 4.0.29, 4.4.13

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Cheahuychou Mao
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-13659 Investigate changes in SERVER-26755: ... Closed
Duplicate
duplicates SERVER-22611 ChunkManager refresh can occasionally... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4, v4.2, v4.0
Sprint: Sharding 2020-06-01
Participants:

 Description   

The collection chunk loading code uses the _exhaustiveFindOnConfig call, which applies 30 seconds of timeout to the entire fetch (not just the individual getMore invocations).

If there is a large number of chunks and the config server fetches take more than 30 seconds in total, the initial chunk loading will never succeed, because each attempt will fail with ExceededTimeLimit and will throw out whatever data was partially loaded on the previous attempt, thus effectively starting from the beginning.



 Comments   
Comment by Githook User [ 03/Feb/22 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-26755 Increase the timeout for find operations against config.chunks

(cherry picked from commit fa03802cb9b42818dd2180f966dd8da64203186a)
Branch: v4.0
https://github.com/mongodb/mongo/commit/3f62170f634d76afd82597b512f0e1ac1656d3ae

Comment by Githook User [ 03/Feb/22 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-26755 Increase the timeout for find operations against config.chunks

(cherry picked from commit fa03802cb9b42818dd2180f966dd8da64203186a)
Branch: v4.2
https://github.com/mongodb/mongo/commit/d7ecec38af5b1b63603519cc4d36fc0532d192e1

Comment by Githook User [ 03/Feb/22 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-26755 Increase the timeout for find operations against config.chunks

(cherry picked from commit fa03802cb9b42818dd2180f966dd8da64203186a)
Branch: v4.4
https://github.com/mongodb/mongo/commit/32d791e2c466ad480b47b050dc0016018775473b

Comment by Cheahuychou Mao [ 19/May/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-26755 Increase the timeout for find operations against config.chunks

Branch: master
https://github.com/mongodb/mongo/commit/fa03802cb9b42818dd2180f966dd8da64203186a

Comment by Cen Zheng [ 18/Mar/20 ]

Hi, we are experiencing this issue with a sharded collection which has more than 20,000,000 chunks in 3.4.6(and 4.0.13). It seems this issue still exists and is not duplicated with SERVER-22611. Would you reopen this issue?

Thanks.

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