[SERVER-84] when replicating capped collection, _id index is created at the target Created: 01/Jun/09  Updated: 07/Mar/14  Resolved: 28/Oct/10

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

Type: Improvement Priority: Minor - P4
Reporter: Aaron Staple Assignee: Eliot Horowitz (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-2019 _id index on capped collection : inco... Closed
Participants:

 Description   

Regardless of whether or not a source capped collection has an _id index, our replication code will create an _id index on the target collection to make op replay detection efficient. As a consequence, insertion into the target collection could potentially be slower than insertion into the source collection, eventually causing the slave to become out of sync if there is a high frequency of writes to the master. One way to resolve this would be to detect replays by verifying the _id of the newest element in the capped collection (the one which will precede the new object to be added if the new object described in the op is in fact added).



 Comments   
Comment by Eliot Horowitz (Inactive) [ 28/Oct/10 ]

SERVER-2019
the other has some updated information

Generated at Thu Feb 08 02:52:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.