[SERVER-21483] Secondary can reorder capped collection inserts with document-level locking - MongoDB Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: 3.0.7
Fix Version/s: 3.0.8, 3.2.0-rc4
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Completed:

3.0.8
Sprint:
QuInt C (11/23/15)

Description

In fillWriterVectors() we distribute inserts to threads based on a hash of the _id and namespace. This means that inserts to capped collections can happen in a different order than the primary.

Attachments

Issue Links

is related to

SERVER-21646 Inserts and updates to replicated capped collections must be single threaded

Closed

Activity

People

Assignee:: Mathias Stearn

Reporter:: Mathias Stearn

Participants:: Githook User, Mathias Stearn

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: Nov 16 2015 07:40:14 PM UTC

Updated:: Dec 03 2015 06:56:28 PM UTC

Resolved:: Nov 20 2015 12:03:08 AM UTC