Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50169

Shard mongod unable to refresh metadata after cluster restore

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible

      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?

            Assignee:
            Unassigned Unassigned
            Reporter:
            joe.caswell@mongodb.com Joe Caswell
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: