-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.18
-
Component/s: Replication
-
None
-
ALL
-
mongod start:
2018-12-21T16:35:55.467+0100 I ASIO [NetworkInterfaceASIO-RS-0] Successfully connected to mongodb001.replset001.app.domain:27017, took 7ms (3 connections now open to mongodb001.replset001.app.domain27017)
2018-12-21T16:36:00.844+0100 I NETWORK [conn10098] received client metadata from 192.168.100.192:44896 conn10098: { driver:
, os: { type: "Linux", name: "Debian GNU/Linux", version: "9", architecture: "x86_64" }, platform: "cfg=0xd15620c9 posix=200809 stdc=201112 CC=GCC 6.3.0 20170516 CFLAGS="-g -O2" LDFLAGS="" / PHP 7.2.13" }
2018-12-21T16:37:27.830+0100 F REPL [repl writer worker 5] writer worker caught exception: 10003 Cannot change the size of a document in a capped collection: 71 != 86 on: { ts: Timestamp 1545406647000|4, h: -308296782776005596, v: 2, op: "u", ns: "app.taskscheduler.jobs", o2:
, o: { $set:
{ status: 3, ended: new Date(1545406647813) } } }
2018-12-21T16:37:27.830+0100 I - [repl writer worker 5] Fatal assertion 16359 CannotGrowDocumentInCappedNamespace: Cannot change the size of a document in a capped collection: 71 != 86 at src/mongo/db/repl/sync_tail.cpp 1087
2018-12-21T16:37:27.830+0100 I - [repl writer worker 5]
***aborting after fassert() failure
Restart results in the same error.
- duplicates
-
SERVER-38724 Under rare conditions, updates to capped collections can cause SECONDARY members to fail
- Closed