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

Shard with replica set name of "config" not properly detected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 2.6.0-rc2
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Start a sharded cluster where one of the shards is a replica set with the name of "config". Try to insert data into a sharded collection and see that the shard does not get used.

      Show
      Start a sharded cluster where one of the shards is a replica set with the name of "config". Try to insert data into a sharded collection and see that the shard does not get used.
    • Sprint:
      Sharding 2019-02-11

      Description

      Inserted data with the following script into the cluster:

      sh.enableSharding("test")
      db.test.ensureIndex({x:1})
      sh.shardCollection("test.test", {x:1})
       
      var i = 0;
      var a = Array(10000).toString()
      for (i = 0; i < 1000; i++) { db.test.insert({x:i, a:a}); }
      

      Sharding status output:

      mongos> sh.status()
      --- Sharding Status ---
        sharding version: {
      	"_id" : 1,
      	"version" : 4,
      	"minCompatibleVersion" : 4,
      	"currentVersion" : 5,
      	"clusterId" : ObjectId("533c6d664fe3c29ccff63fc2")
      }
        shards:
      	{  "_id" : "config",  "host" : "config/sv.local:30011,sv.local:30012,sv.local:30013" }
      	{  "_id" : "shard2",  "host" : "shard2/sv.local:30021,sv.local:30022,sv.local:30023" }
      	{  "_id" : "shard3",  "host" : "shard3/sv.local:30031,sv.local:30032,sv.local:30033" }
        databases:
      	{  "_id" : "admin",  "partitioned" : false,  "primary" : "config" }
      	{  "_id" : "test",  "partitioned" : true,  "primary" : "shard2" }
      		test.test
      			shard key: { "x" : 1 }
      			chunks:
      				shard2	4
      				shard3	5
      			{ "x" : { "$minKey" : 1 } } -->> { "x" : 0 } on : shard2 Timestamp(2, 1)
      			{ "x" : 0 } -->> { "x" : 33 } on : shard2 Timestamp(1, 3)
      			{ "x" : 33 } -->> { "x" : 111 } on : shard2 Timestamp(3, 0)
      			{ "x" : 111 } -->> { "x" : 190 } on : shard2 Timestamp(4, 0)
      			{ "x" : 190 } -->> { "x" : 269 } on : shard3 Timestamp(4, 1)
      			{ "x" : 269 } -->> { "x" : 347 } on : shard3 Timestamp(2, 8)
      			{ "x" : 347 } -->> { "x" : 783 } on : shard3 Timestamp(3, 2)
      			{ "x" : 783 } -->> { "x" : 863 } on : shard3 Timestamp(3, 4)
      			{ "x" : 863 } -->> { "x" : { "$maxKey" : 1 } } on : shard3 Timestamp(3, 5)
       
      mongos>
      

      I saw in the logs:

      2014-04-02T15:34:32.347-0400 [WriteBackListener-sv.local:20001] warning: Monitor not found for a known shard: config
      

      For one of my previous attempts (although I didn't see it for the one where I have the sharding status shown above).

        Attachments

          Activity

            People

            Assignee:
            janna.golden Janna Golden
            Reporter:
            sverch Shaun Verch
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: