[SERVER-49400] Differenciate VectorClock persist behavior based on cluster role Created: 09/Jul/20  Updated: 29/Oct/23  Resolved: 27/Jul/20

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-48717 Implement the persist/recover functio... Closed
is depended on by SERVER-49192 Persist the VectorClock for configTim... Closed
Problem/Incident
causes SERVER-51328 Do not pass entire namespace string t... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-07-13, Sharding 2020-07-27, Sharding 2020-08-10
Participants:

 Description   

The persist method introduced in SERVER-48717 should behave in different ways depending on the cluster role.

  • Config server: don’t do anything because configTime and topologyTime are guaranteed from the oplog (last optimes on oplog)
  • Shard primary: call create/update with majority write concern
  • Shard secondary: call waitForInMemoryVectorClockToBePersisted on the primary (a PersistVectorClockCommand need to be created)


 Comments   
Comment by Githook User [ 27/Jul/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-49400 Differenciate VectorClock persist behavior based on cluster role
Branch: master
https://github.com/mongodb/mongo/commit/4dab9b9781f943fcd7e2f15e61bdbce9953d0e23

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