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

Error in writing into MongoDB: !loc.isNull()

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Gone away
    • Affects Version/s: 2.4.5
    • Fix Version/s: None
    • Component/s: Write Ops
    • Labels:
    • Operating System:
      ALL

      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 }

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: