[SERVER-22530] improve capped collection replicated inserts Created: 09/Feb/16  Updated: 19/Dec/16  Resolved: 11/Feb/16

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Steps To Reproduce:

Run the insert_capped.js workload on a replica set to see the issue.

Sprint: Repl 10 (02/19/16)
Participants:

 Description   

Vectored insert does not support inserting into a capped collection, so if you do more than a light load of inserts into a capped collection, secondaries will flood their logs with:

2016-02-08T17:00:21.539-0500 E REPL     [repl writer worker 13] Error applying inserts in bulk  :: caused by :: 151 Can't batch inserts into indexed capped collections trying first insert as a lone insert

This also severely impacts performance since every batch insert throws and catches an exception.

We should avoid trying to do vector inserts on capped collections. We can use the CachingCappedChecker for this, or some other clever technique.



 Comments   
Comment by Githook User [ 11/Feb/16 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-22530 do not attempt bulk inserts on capped collections while replciating
Branch: master
https://github.com/mongodb/mongo/commit/5dd2b06d0236c73db09fb2a9411a7772e424afb3

Comment by Matt Dannenberg [ 10/Feb/16 ]

Where does the insert_capped.js workload live?

Generated at Thu Feb 08 04:00:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.