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

cleanupOrphaned should not need remote metadata refresh if metadata exists

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.6.0-rc0
    • Affects Version/s: 2.5.4
    • Component/s: Logging, Sharding
    • None
    • ALL

      By design, we should be able to safely clean up orphaned data using only local information (unless we are not sure if we're a shard or not). Keep thing simple by only refreshing if our local information is unset (i.e. needMetadataFor() is false).

      Previously was a ticket tracking error messages:

      "failed to refresh shard metadata: cannot refresh metadata for foo.bar before shard name has been set"

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            matt.dannenberg Matt Dannenberg
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: