[SERVER-6469] config.changelog not integrated with locking in operations themselves Created: 16/Jul/12  Updated: 06/Dec/22  Resolved: 03/May/18

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

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

... resulting in changelog entries potentially being reordered in arbitrary ways over short time periods.

It's difficult to create automated tools if we can't trust the changelog ordering - even small differences could result in failure. We can try to make our tools "guess", but this is A) hard to do in a portable way and B) won't ever be 100% correct.


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