[SERVER-30621] Ensure there is routing metadata before doing range deletion in moveChunk Created: 11/Aug/17  Updated: 30/Oct/23  Resolved: 22/Sep/17

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-09-11, Sharding 2017-10-02
Participants:
Linked BF Score: 0

 Description   

Migration fails to refresh metadata after a successful migration commit because the config server is shutting down. This is logged here. This failed remote metadata refresh causes the chunk metadata to get cleared. However, this code here is returning a successful migration commit status, so the shard moveChunk command continues on to do range deletion like everything is fine. And then MetadataManager::cleanUpRange invariants because there is no chunk metadata.



 Comments   
Comment by Githook User [ 22/Sep/17 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: SERVER-30621 Ensure chunk metadata exists when cleanUpRange is called in moveChunk
Branch: master
https://github.com/mongodb/mongo/commit/8e8b048ebf6ec989eb3a54e45cf6cb5892442748

Comment by Dianna Hohensee (Inactive) [ 21/Sep/17 ]

ian.whalen, the LGTM'ed solution is hanging in the slow1 suite. I've been trying to debug it this week.

Comment by Ian Whalen (Inactive) [ 21/Sep/17 ]

dianna.hohensee looks like this was LGTMd? Was it pushed? It's currently blocking one of our top 3 build failures.

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