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

[rsSync] warning: DR102 too much data written uncommitted 314.577MB

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.6.4
    • Component/s: Replication
    • Labels:
      None
    • ALL
    • Hide

      Install 2.6.6 onto debian 7.7, set up a 3 node cluster (one is an arbiter node).

      Watch the mongo.log on the secondary.

      Show
      Install 2.6.6 onto debian 7.7, set up a 3 node cluster (one is an arbiter node). Watch the mongo.log on the secondary.

      I'm seeing the problem (or similar to) as reported in https://jira.mongodb.org/browse/SERVER-6925

      2014-12-17T15:19:04.998+0000 [rsSync] warning: DR102 too much data written uncommitted 314.577MB
2014-12-17T15:19:06.106+0000 [rsSync] local.oplog.rs warning assertion failure _intents.size() < 2000000 src/mongo/db/dur_commitjob.h 112
2014-12-17T15:19:06.116+0000 [rsSync] local.oplog.rs 0x11e6111 0x1187e49 0x116be5f 0xa64c8f 0xa64e2b 0xa64ea2 0xa64fd3 0xa65047 0xa5deba 0xf2663f 0xf2295d 0xf2451f 0xf29aea 0xf29b4f 0xf32ddf 0xf32770 0x8b601f 0x8b693a 0xe5667f 0xeaf91b
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11e6111]
 /usr/bin/mongod(_ZN5mongo10logContextEPKc+0x159) [0x1187e49]
 /usr/bin/mongod(_ZN5mongo9wassertedEPKcS1_j+0x17f) [0x116be5f]
 /usr/bin/mongod(_ZN5mongo3dur9CommitJob4noteEPvi+0x31f) [0xa64c8f]
 /usr/bin/mongod(_ZN5mongo3dur18ThreadLocalIntents8_unspoolEv+0x4b) [0xa64e2b]
 /usr/bin/mongod(_ZN5mongo3dur18ThreadLocalIntents7unspoolEv+0x52) [0xa64ea2]
 /usr/bin/mongod(_ZN5mongo3dur18ThreadLocalIntents4pushERKNS0_11WriteIntentE+0x83) [0xa64fd3]
 /usr/bin/mongod(_ZN5mongo3dur11DurableImpl18declareWriteIntentEPvj+0x67) [0xa65047]
 /usr/bin/mongod(_ZN5mongo3dur11DurableImpl10writingPtrEPvj+0xa) [0xa5deba]
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails13addDeletedRecEPNS_13DeletedRecordENS_7DiskLocE+0x11f) [0xf2663f]
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails7compactEv+0x25d) [0xf2295d]
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails11cappedAllocEPNS_10CollectionERKNS_10StringDataEi+0x26f) [0xf2451f]
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails6_allocEPNS_10CollectionERKNS_10StringDataEi+0x2a) [0xf29aea]
 /usr/bin/mongod(_ZN5mongo16NamespaceDetails5allocEPNS_10CollectionERKNS_10StringDataEi+0x5f) [0xf29b4f]
 /usr/bin/mongod(_ZN5mongo19CappedRecordStoreV111allocRecordEii+0x3f) [0xf32ddf]
 /usr/bin/mongod(_ZN5mongo17RecordStoreV1Base12insertRecordEPKcii+0x60) [0xf32770]
 /usr/bin/mongod(_ZN5mongo10Collection15_insertDocumentERKNS_7BSONObjEbPKNS_16PregeneratedKeysE+0x7f) [0x8b601f]
 /usr/bin/mongod(_ZN5mongo10Collection14insertDocumentERKNS_7BSONObjEbPKNS_16PregeneratedKeysE+0x22a) [0x8b693a]
 /usr/bin/mongod(_ZN5mongo11_logOpObjRSERKNS_7BSONObjE+0x33f) [0xe5667f]
 /usr/bin/mongod(_ZN5mongo7replset8SyncTail15applyOpsToOplogEPSt5dequeINS_7BSONObjESaIS3_EE+0x4b) [0xeaf91b]

      Given that this was reported as fixed in 2.2.x and 2.3.x series I'm a little unsure if this is new or another manifest of the same bug.

      The data inserted into mongo is very small (in the order of kilobytes) and it's an average of a couple of MB per hour - so not exactly large data volumes to replicate.

      # mongod --version
db version v2.6.4
2014-12-18T15:10:45.077+0000 git version: 3a830be0eb92d772aa855ebb711ac91d658ee910

        1. mongodb.log.5.gz
          1.55 MB

            Assignee:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Reporter:
            craiggenner Craig Genner
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: