[SERVER-46330] Delete oplogFetcherUsesExhaust server parameter if running last-stable binary Created: 21/Feb/20  Updated: 29/Oct/23  Resolved: 24/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-03-09
Participants:
Linked BF Score: 36

 Description   

When starting a replica set, we re-use the options for all the nodes. For multiversion replica sets, this means that if a node set the oplogFetcherUsesExhaust server parameter to false, if we don't reset or delete the parameter, the next node will inherit that parameter. If the next node is running 4.2, this means that it will try to set the parameter, but fail because it doesn't know about it.

We should delete the parameter in all cases when running with a last-stable bin version to be safe.



 Comments   
Comment by Githook User [ 24/Feb/20 ]

Author:

{'name': 'Samyukta Lanka', 'username': 'lankas', 'email': 'samy.lanka@mongodb.com'}

Message: SERVER-46330 Delete 'oplogFetcherUsesExhaust' server parameter if running last-stable binary
Branch: master
https://github.com/mongodb/mongo/commit/56f899f7a7fd77234d468cc28468950e4d38477d

Generated at Thu Feb 08 05:11:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.