[SERVER-13605] Error in writing into MongoDB: !loc.isNull() Created: 16/Apr/14  Updated: 10/Dec/14  Resolved: 20/May/14

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: 2.4.5
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Yang Assignee: Thomas Rueckstiess
Resolution: Done Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

MongoDB Version: 2.4.5
OS: Win Server 2008 R2 SP1
Config Server: 3 instances.
Sharding: 2 shards
Replica set size: 3

Issue:
MongoDB is readable but not fully writable. For example, issuing a command as below:

db.collection.update({Active:true}, {$set: {field: value}}, false, true);

The command will update only one record and then receiving error message simply saying "!loc.isNull()".

I have also observed frequent log entries in mongos.log

Wed Apr 16 14:55:06.541 [LockPinger] warning: distributed lock pinger 'configserver1:port1,configserver2:port2,configserv3:port3/mongosserver:port5:
1397543735:41' detected an exception while pinging. :: caused by :: update not consistent  ns: config.lockpings query:
{ _id: "mongosserver:port5:1397543735:41" } update: { $set: { ping: new Date(1397631305839) } } gle1: { err: "!loc.isNull()",
n: 0, connectionId: 4481, waited: 126, ok: 1.0 } gle2: { updatedExisting: true, n: 1, lastOp: Timestamp 1397631305000|1
, connectionId: 4468, waited: 69, err: null, ok: 1.0 }



 Comments   
Comment by Thomas Rueckstiess [ 20/May/14 ]

Hi Guoming,

We haven't heard back from you and can't continue the diagnosis without additional information. I'll go ahead and resolve the ticket now. If this is still an issue and you would like to follow up, feel free to re-open it and provide the log files requested in the comments above.

Kind Regards,
Thomas

Comment by Thomas Rueckstiess [ 29/Apr/14 ]

Hi Guoming,

Is this still an issue? We still need some more information and the log files from the shards and config servers to diagnose the issue. Can you please attach them?

Regards,
Thomas

Comment by Eliot Horowitz (Inactive) [ 16/Apr/14 ]

Can you send the logs from the shard primaries and config servers?

Generated at Thu Feb 08 03:32:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.