[SERVER-36773] Test replication paths for a v4.2 mongod receiving a <db>.system.indexes oplog entry from a v4.0 primary Created: 20/Aug/18  Updated: 22/Aug/18  Resolved: 21/Aug/18

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Storage NYC 2018-08-27
Participants:

 Description   

SERVER-36015 is removing system.indexes special handling in v4.2, except for the replication paths because a v4.0 mongod can still do inserts to <db>.system.indexes collections per SERVER-36714.

This ticket is adding integration testing specifically to ensure a v4.2 mongod continues to correctly handle v4.0 mongod's <db>.system.indexes inserts along its replication paths. The testing should be removed in the v4.4 dev cycle.

The multi-version testing should likely include testing of an <db>.system.indexes insert along the following replication paths:

  • regular steady-state replication
  • applyOps
  • initial sync
  • recoverable rollback
    I'd suggest a set up with a v4.0 primary and v4.2 secondary.


 Comments   
Comment by Dianna Hohensee (Inactive) [ 21/Aug/18 ]

It turns out that although document_source_out_replace_coll.cpp ostensibly does an insert on system.indexes in v4.0, internally a v4.0 mongod converts that to a createIndexes oplog entry in replication. So we therefore need no backwards compatibility with v4.0 for system.indexes writes because there aren't any internally.

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