[SERVER-75326] Add support for flushing sizeStorer to disk manually Created: 27/Mar/23  Updated: 27/Oct/23  Resolved: 04/Apr/23

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-74684 Size storer not being flushed periodi... Closed
Related
Assigned Teams:
Storage Execution
Participants:
Case:

 Description   

In some cases initial sync might lead to the invalid sizeStorer values getting passed into the secondary. This is not a data consistency issue since those values can be manually fixed by performing a validate command.

Visually though, these values can lead to incorrect decisions or even surprise users by providing a value much lower than expected and mistaking it for data loss even if nothing has actually been lost.

One option would be to add support for fsync in order to only syncing journalled tables. This would limit I/O impact and flush the sizeStorer metadata into disk.

Another option would be to add a new command to perform this.



 Comments   
Comment by Connie Chen [ 04/Apr/23 ]

SERVER-74684 should have addressed this

Comment by Yuhong Zhang [ 28/Mar/23 ]

Reevaluate this ticket after SERVER-74684

Generated at Thu Feb 08 06:29:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.