Replica Sets and 'warning: cursor loc null does not match byLoc'

[Łukasz Jagiełło]

Hi,

I have MongoDB in configuration with Replica Sets (2 mongo + arbiter).
Now I want to add 3rd mongo, so I configure mongo at 3rd node, add
next replica in configuration and mongo start sync data.

Everything works fine until got this:

#v+
Thu Oct 14 11:45:31 [rs_sync] replSet initialSyncOplogApplication 6900000
Thu Oct 14 11:46:43 [rs_sync] replSet initialSyncOplogApplication 7000000
Thu Oct 14 11:48:13 [rs_sync] replSet initialSyncOplogApplication 7100000
Thu Oct 14 11:48:16 [rs_sync] warning: can't find plugin [1]
Thu Oct 14 11:48:16 [rs_sync] warning: can't find plugin [1]
Thu Oct 14 11:48:16 [rs_sync] warning: can't find plugin [1]
Thu Oct 14 11:48:16 [rs_sync] warning: can't find plugin [1]
Thu Oct 14 12:00:28 [rs_sync] database_name.table warning: cursor loc
null does not match byLoc position 6:1876540 !
Thu Oct 14 12:03:48 [rs_sync] database_name.table warning: cursor loc
null does not match byLoc position 5:176c18dc !
Thu Oct 14 12:04:01 [rs_sync] database_name.table warning: cursor loc
null does not match byLoc position 5:52959914 !
Thu Oct 14 12:04:27 [rs_sync] database_name.table warning: cursor loc
null does not match byLoc position 7:235e9264 !
Thu Oct 14 12:07:23 [rs_sync] replSet initial sync finishing up
Thu Oct 14 12:07:23 [rs_sync] replSet set minValid=4cb6ca34:1
Thu Oct 14 12:07:23 [rs_sync] building new index on { _id: 1 } for
local.replset.minvalid
Thu Oct 14 12:07:23 [rs_sync] done for 0 records 0.05secs
Thu Oct 14 12:07:23 [rs_sync] replSet initial sync done
Thu Oct 14 12:07:25 [rs_sync] replSet SECONDARY
#v-

Why got such warnings ? Try two times make full sync (from empty db)
and at first time got 2 warnings, second time got 4 warnings.

At both times 2 and 4 items missing when i do count at primary vs secondary.

Replica sets status looks like this:

#v+
> rs.status()
{
"set" : "some_name",
"date" : "Thu Oct 14 2010 14:04:52 GMT+0200 (CEST)",
"myState" : 1,
"members" : [
{
"_id" : 0,
"name" : "10.0.0.202:27018",
"health" : 1,
"state" : 1,
"self" : true
},
{
"_id" : 1,
"name" : "10.0.0.201:27018",
"health" : 1,
"state" : 2,
"uptime" : 81566,
"lastHeartbeat" : "Thu Oct 14 2010 14:04:52 GMT+0200 (CEST)"
},
{
"_id" : 2,
"name" : "10.0.0.201:30000",
"health" : 1,
"state" : 7,
"uptime" : 81566,
"lastHeartbeat" : "Thu Oct 14 2010 14:04:51 GMT+0200 (CEST)"
},
{
"_id" : 3,
"name" : "10.0.0.203:27018",
"health" : 1,
"state" : 2,
"uptime" : 12821,
"lastHeartbeat" : "Thu Oct 14 2010 14:04:52 GMT+0200 (CEST)"
}
],
"ok" : 1
}
#v-

id: 3 <- that 3rd node

MongoDB 1.6.3
CentOS 5.3

Regards
--
Łukasz Jagiełło
lukasz<at>jagiello<dot>org

[dwight_10gen]

will investigate.

what version?

are you using geospatial indexes?

[Łukasz Jagiełło]

2010/10/14 dwight_10gen <dwi...@10gen.com>:
> will investigate.
>
> what version?

Mongo 1.6.3 (build from sources)

> are you using geospatial indexes?

No

[David M]

Dwight: See CS-154.

[Eliot Horowitz]

The plugin warning is probably because you created an index like { x :
"1" } instead of { x : 1 }
you should use { x : 1 } and { x : "1" } may be removed at some point
as its not correct.

The other warning isn't harmful, and is fixed in master.

2010/10/14 Łukasz Jagiełło <jagiell...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
>

[Łukasz Jagiełło]

2010/10/14 Eliot Horowitz <elioth...@gmail.com>:

> The plugin warning is probably because you created an index like { x :
> "1" } instead of { x : 1 }
> you should use { x : 1 } and { x : "1" } may be removed at some point
> as its not correct.
>
> The other warning isn't harmful, and is fixed in master.

Thanks, after fix indexes replication works nice, without any warnings at sync.