[SERVER-45338] Make moveChunk robust to maxTimeMS expiring Created: 02/Jan/20  Updated: 29/Oct/23  Resolved: 10/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-30179 moveChunk doesn't obey maxTimeMS cons... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24
Participants:
Linked BF Score: 20

 Description   

In FCV 4.4, moveChunk contains a MigrationCoordinator that needs to be driven to completion.



 Comments   
Comment by Githook User [ 10/Feb/20 ]

Author:

{'username': 'saltzm', 'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}

Message: SERVER-45338 Make moveChunk robust to maxTimeMS expiring (fix auth after revert)
Branch: master
https://github.com/mongodb/mongo/commit/32770d4dcb8317dc7c4f03fe120fc5682821d137

Comment by Githook User [ 05/Feb/20 ]

Author:

{'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}

Message: Revert "SERVER-45338 Make moveChunk robust to maxTimeMS expiring"

This reverts commit 2985a71befe421902b5d15e9567e3b449e65ecdd.

delete mode 100644 jstests/sharding/move_chunk_respects_maxtimems.js
Branch: master
https://github.com/mongodb/mongo/commit/bb5f249a0d1a69c2e42cda5c255b705a24d58ff9

Comment by Matthew Saltz (Inactive) [ 05/Feb/20 ]

Revert is in the queue

Comment by Matthew Saltz (Inactive) [ 05/Feb/20 ]

Sure, I can revert. Not sure what's going on.

Comment by William Schultz (Inactive) [ 05/Feb/20 ]

Unless you have an immediate fix, can you revert?

Comment by Matthew Saltz (Inactive) [ 05/Feb/20 ]

Thanks for the heads up. It passed on my patch build Maybe a merge issue. Will look into it

Comment by William Schultz (Inactive) [ 05/Feb/20 ]

matthew.saltz It looks like this commit may have broken multiversion_auth suites on required builder. Can you revert the commit?

Comment by Githook User [ 05/Feb/20 ]

Author:

{'username': 'saltzm', 'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}

Message: SERVER-45338 Make moveChunk robust to maxTimeMS expiring

create mode 100644 jstests/sharding/move_chunk_respects_maxtimems.js
Branch: master
https://github.com/mongodb/mongo/commit/2985a71befe421902b5d15e9567e3b449e65ecdd

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