[SERVER-50169] Shard mongod unable to refresh metadata after cluster restore Created: 06/Aug/20  Updated: 06/Aug/20  Resolved: 06/Aug/20

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

Type: Question Priority: Major - P3
Reporter: Joe Caswell Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

MongoDB: 3.6.13
FCV: 3.4

Customer restored a 6-shard cluster roughly following the process at https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/#restore-a-sharded-cluster

Currently queries through the mongos are failing with `setShardVersion failed`, which corresponds with the mongod logging failure to refresh metdata with ShardNotFound:

Representative mongos and shard mongod logs are attached, additional log and config dump are available if needed.

What is causing the shard not found error?
What can the customer do to work around this?



 Comments   
Comment by Joe Caswell [ 06/Aug/20 ]

Wrong project

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