[SERVER-15303] passes >= maxPasses in oplog Created: 18/Sep/14  Updated: 22/Sep/14  Resolved: 18/Sep/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Thomas Hjorslev Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6981 maxPasses assertion (on allocation fa... Closed
Operating System: ALL
Steps To Reproduce:

Seems to happen randomly (based on what is at the tail of the oplog?)

Participants:

 Description   

While running a major batch run, which updates a lot of documents, we are occasionally seeing this error:

MongoDB.Driver.WriteConcernException: WriteConcern detected an error 'passes >= maxPasses in NamespaceDetails::cappedAlloc: ns: local.oplog.rs, len: 1060528, maxPasses: 35352, _maxDocsInCapped: 2147483647, nrecords: 8019946, datasize: 8426545700'. (Response was { "ok" : 1, "code" : 10345, "err" : "passes >= maxPasses in NamespaceDetails::cappedAlloc: ns: local.oplog.rs, len: 1060528, maxPasses: 35352, _maxDocsInCapped: 2147483647, nrecords: 8019946, datasize: 8426545700", "n" : NumberLong(0), "updatedExisting" : false }).


It causes an exception in the client (.NET) application.
Apparently the error is generated in cap.cpp
As far as I can tell from the error message, the document is 1060528, and it gives up after having removed 35352 documents from the oplog.
We have seen this error 8 times since July 5 (on a job that runs daily).
len varies between 200k and 1600k



 Comments   
Comment by Thomas Hjorslev [ 22/Sep/14 ]

Thank you ramon.fernandez for your feedback.
As far as I can tell, there is nothing we can do to work around the problem, except re-running the operation that failed, at a later time.
SERVER-6981 seems to be planned for the 2.7 release, so I guess we will wait for that.

Comment by Ramon Fernandez Marina [ 19/Sep/14 ]

tmh@fundconnect.com, there're is further information on this issue on SERVER-15265.

Comment by Ramon Fernandez Marina [ 18/Sep/14 ]

tmh@fundconnect.com, looks like you're running into SERVER-6981, which can happen when inserting a large document into the oplog. Marking this ticket as a duplicate, feel free to watch/vote for SERVER-6981.

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