[SERVER-62698] Do not clear filtering metadata on secondaries upon minor version updates Created: 18/Jan/22  Updated: 06/Dec/22  Resolved: 04/Jul/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.2.0, 4.2.17, 4.4.10, 5.0.5, 5.1.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-67078 Advancing just the minor version on t... Closed
Gantt Dependency
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

As minor version updates are not implying a change of ownership, it should not be needed to clear the filtering metadata as long as a major version doesn't change.

The current logic is the following: while refreshing, the refreshing flag is set to true and - after updating collection/chunks entries - the field is set to false. An observer is reacting to the "set to false" event by registering a change that on commit causes the filtering metadata to be cleared up.

Objective of this ticket is to avoid clearing the filtering metadata on minor versions updates. The following could be a way to implement the solution:

  • "Play" with the refreshing field in a different way:
    • Set it to true and then false on major version updates
    • Set it to true and then unset on minor version updates


 Comments   
Comment by Kaloian Manassiev [ 04/Jul/22 ]

Closing it as duplicate of SERVER-67078.

Comment by Connie Chen [ 03/Feb/22 ]

garaudy.etienne

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