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

Issue with Sharding Collection SplitVector timeout

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.4
    • Component/s: Sharding
    • None
    • ALL
    • Sharding 15 (06/03/16)

      Hi Team,

      My problem is when I run the shardcollection command, nothing happens and in some cases I have a timeout

      { "code" : 50, "ok" : 0, "errmsg" : "Operation timed out" }

      I do :

      mongos> use admin
      
      mongos> db.runCommand( { shardCollection : "Dev.link" , key : { urlHash : 1 } , unique : true } );
      

      In the logfile :

      #1# 2016-04-02T23:55:38.286+0200 I NETWORK  [initandlisten] connection accepted from 192.168.0.101:39391 #14 (6 connections now open)
      
      #2# 2016-04-02T23:58:51.179+0200 I COMMAND  [conn9] command admin.$cmd command: checkShardingIndex { checkShardingIndex: "link.link", keyPattern: { urlHash: 1.0 } } keyUpdates:0 writeConflicts:0 numYields:541544 reslen:134 locks:{ Global: { acquireCount: { r: 1083090 } }, Database: { acquireCount: { r: 541545 } }, Collection: { acquireCount: { r: 541545 } } } protocol:op_command 231824ms
      
      #3# 2016-04-02T23:58:51.256+0200 I SHARDING [conn14] request split points lookup for chunk repolink2.link { : MinKey } -->> { : MaxKey }
      2016-04-02T23:59:23.096+0200 W SHARDING [conn14] Finding the split vector for repolink2.link over { urlHash: 1.0 } keyCount: 187454 numSplits: 369 lookedAt: 135495 took 31839ms
      
      #4# 2016-04-02T23:59:23.096+0200 I COMMAND  [conn14] command admin.$cmd command: splitVector { splitVector: "repolink2.link", keyPattern: { urlHash: 1.0 }, min: { urlHash: MinKey }, max: { urlHash: MaxKey }, maxChunkSizeBytes: 1073741824, maxSplitPoints: 0, maxChunkObjects: 0 } keyUpdates:0 writeConflicts:0 numYields:541456 reslen:32528 locks:{ Global: { acquireCount: { r: 1082914 } }, Database: { acquireCount: { r: 541457 } }, Collection: { acquireCount: { r: 541457 } } } protocol:op_command 31839ms
      
      #5# 2016-04-02T23:59:23.096+0200 I NETWORK  [conn14] end connection 192.168.0.101:39391 (5 connections now open)
      

      I have 3 configserver, 1 mongos, 2 mongodb.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            PM Pierre MOELO [X]
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: