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

Sharded work being done on config server secondary

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 18 (08/05/16)

      In tests I see non-primary replicas printing lines like this during replication, in the applier threads, during initial sync:

      [js_test:movechunk_with_default_paranoia] 2016-07-22T20:41:36.934+0000 c22264| 2016-07-22T20:41:36.934+0000 I SHARDING [initial sync] Marking collection as not sharded.
      ...
      [js_test:movechunk_with_default_paranoia] 2016-07-22T20:41:45.946+0000 c22262| 2016-07-22T20:41:45.946+0000 I SHARDING [rsSync] Marking collection as not sharded.
      ...
      [js_test:movechunk_with_default_paranoia] 2016-07-22T20:41:47.017+0000 c22264| 2016-07-22T20:41:47.017+0000 I REPL     [ReplicationExecutor] Member ip-10-45-2-165:22262 is now in state PRIMARY
      [js_test:movechunk_with_default_paranoia] 2016-07-22T20:41:47.018+0000 c22264| 2016-07-22T20:41:47.017+0000 I REPL     [rsBackgroundSync] syncing from: ip-10-45-2-165:22262
      [js_test:movechunk_with_default_paranoia] 2016-07-22T20:41:47.018+0000 c22264| 2016-07-22T20:41:47.018+0000 I SHARDING [repl writer worker 15] Marking collection as not sharded.
      

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: