top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Seeing key seems to have moved in the index too often in MangoDB?

+1 vote

I have a collection (say X) in mongodb replicaset which is updated quite frequently. X is part of a database where there are about 10-12 collections with usePowerodfSize enabled but collection X does not have this setting enabled. After enabling usepowerof2size on other collections I have started noticing "key seems to have moved in the index, refinding. 71:4ca18000" error show up very often. Every time this happens, the disk I/o shoots up very high, mongodb process starts running very hot. As a result the connection to other members of the replicaset starts getting affected and they go completely out of sync.

I read some articles online saying that "key seems to have moved" if printed very in-frequently can be ignored. But no where i found an answer to what if this shows up very frequently and what does this indicate.

Any help would be greatly appreciated. (I use mongodb 2.4.9Everything i have mentioned above is as observed from the PRIMARY logs.)

posted Jun 21, 2015 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

Similar Questions
+1 vote

We are running MongoDB 3.0 with wiredTiger storage engine and wiredTigerCacheSizeGB is 24.
Now, I want to increase the wiredTigerCacheSizeGB value from 24 to 32. Is it possible to increase this variable without restart the service ?

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.