2016-06-20 9 views
2

MongoDB Version: 3.0.8 Motor: WiredTigerMongoDB - Sharding migrateThread langer Lauf seit 3 ​​Stunden

Der Balancer ist zu langsam ~ 30MB Futter zu migrieren, dass aufgrund uns lange laufender Anfragen beobachtet, das ist die besagt, dass sein mehr als 3 Stunden gelaufen. Bitte schlage mich vor.

Die lang laufende Ausgabe von db.currentOp() angehängt. Danke, Albert

------ Long Running Query ---- 

{ 
    "desc" : "migrateThread", 
    "threadId" : "0x95d26a000", 
    "opid" : "u001b_s2_rs:-1345098410", 
    "active" : true, 
    "secs_running" : 9360, 
    "microsecs_running" : NumberLong("9360370895"), 
    "op" : "none", 
    "ns" : "deviceStateEvent.deviceStateEvent", 
    "query" : { 

    }, 
    "msg" : "step 2 of 5", 
    "numYields" : 0, 
    "locks" : { 

    }, 
    "waitingForLock" : false, 
    "lockStats" : { 
     "Global" : { 
      "acquireCount" : { 
       "r" : NumberLong(126582), 
       "w" : NumberLong(126580) 
      } 
     }, 
     "Database" : { 
      "acquireCount" : { 
       "r" : NumberLong(1), 
       "w" : NumberLong(126579), 
       "W" : NumberLong(1) 
      } 
     }, 
     "Collection" : { 
      "acquireCount" : { 
       "r" : NumberLong(1), 
       "w" : NumberLong(63290), 
       "W" : NumberLong(1) 
      } 
     }, 
     "oplog" : { 
      "acquireCount" : { 
       "w" : NumberLong(63288) 
      } 
     } 
    } 
} 

{ 
    "desc" : "conn514744", 
    "threadId" : "0x4423e3400", 
    "connectionId" : 514744, 
    "opid" : "u001b_s0_rs:2109828171", 
    "active" : true, 
    "secs_running" : 9360, 
    "microsecs_running" : NumberLong("9360954810"), 
    "op" : "query", 
    "ns" : "deviceStateEvent.deviceStateEvent", 
    "query" : { 
     "$msg" : "query not recording (too large)" 
    }, 
    "client_s" : "10.99.8.121:45784", 
    "msg" : "step 3 of 6", 
    "numYields" : 1063, 
    "locks" : { 

    }, 
    "waitingForLock" : false, 
    "lockStats" : { 
     "Global" : { 
      "acquireCount" : { 
       "r" : NumberLong(2130), 
       "w" : NumberLong(1), 
       "R" : NumberLong(1) 
      } 
     }, 
     "Database" : { 
      "acquireCount" : { 
       "r" : NumberLong(1064), 
       "w" : NumberLong(1) 
      } 
     }, 
     "Collection" : { 
      "acquireCount" : { 
       "r" : NumberLong(1064), 
       "W" : NumberLong(1) 
      } 
     } 
    } 

------- Balancer Error ----------- 

balancer: 
     Currently enabled: no 
     Currently running: no 
     Failed balancer rounds in last 5 attempts: 0 
     Migration Results for the last 24 hours: 
       116 : Success 
       1 : Failed with error 'chunk too big to move', from u001b_s4_rs to u001b_s3_rs 
       9 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 7 deletes from previous migration', from u001b_s2_rs to u001b_s4_rs 
       402 : Failed with error 'data transfer error', from u001b_s0_rs to u001b_s3_rs 
       322 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 6 deletes from previous migration', from u001b_s2_rs to u001b_s4_rs 
       8 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 7 deletes from previous migration', from u001b_s0_rs to u001b_s4_rs 
       6 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 8 deletes from previous migration', from u001b_s0_rs to u001b_s4_rs 
       1 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 8 deletes from previous migration', from u001b_s1_rs to u001b_s4_rs 
       1 : Failed with error 'chunk too big to move', from u001b_s4_rs to u001b_s1_rs 
       2 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 7 deletes from previous migration', from u001b_s1_rs to u001b_s4_rs 
       387 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 6 deletes from previous migration', from u001b_s0_rs to u001b_s4_rs 
       35 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 2 deletes from previous migration', from u001b_s0_rs to u001b_s2_rs 
       15 : Failed with error 'chunk too big to move', from u001b_s0_rs to u001b_s3_rs 
       2 : Failed with error 'chunk too big to move', from u001b_s0_rs to u001b_s2_rs 
       192 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 6 deletes from previous migration', from u001b_s1_rs to u001b_s4_rs 
       23 : Failed with error 'chunk too big to move', from u001b_s0_rs to u001b_s1_rs 
       5 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 8 deletes from previous migration', from u001b_s2_rs to u001b_s4_rs 
       77 : Failed with error 'moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 1 deletes from previous migration', from u001b_s0_rs to u001b_s2_rs 
+0

Wurde dieses Problem für Sie gelöst? Wenn das so ist, wie? Ich denke, das Problem, das wir gerade haben, ist sehr ähnlich. Aus diesem Grund können wir die kartenreduzierten Statistiken nicht in die Sammlung schreiben. – Exander

Antwort

0

Es gibt einige Löschungen verbleiben, so ist es nicht erlaubt, neue Stücke zu akzeptieren.

Zuerst müssen Sie, damit Sie Balancer: Zum Mongos und laufen sh.setBalancerState(true)

Dies könnte für Sie arbeiten

  1. Zum Scherbe: u001b_s4_rs
  2. gehen Konsole mongo und ab Schritt Ihr primärer Knoten.

    rs.stepDown()

und wieder Status überprüfen.