[SERVER-20886] ensure all uses of rsConfig indexes confirm they are from a matching config version before use Created: 12/Oct/15  Updated: 06/Dec/22  Resolved: 20/Jul/17

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

Type: Task Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-26990 Unify tracking of secondary state bet... Closed
Assigned Teams:
Replication
Sprint: Repl B (10/30/15)
Participants:

 Description   

If the index is from a different config version, it could point to something incorrect or even nothing at all.



 Comments   
Comment by Spencer Brody (Inactive) [ 20/Jul/17 ]

We've been fixing these as we come across them, but aren't planning a dedicated code audit just for this.

Comment by Scott Hernandez (Inactive) [ 12/Oct/15 ]

This is especially important when passing an index as a parameter to the Topology Coordinator via the Executor, since execution could be delayed or scheduled after a config change. The final check should probably always be done by the Topology Coordinator since it holds the authoritative config (and version).

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