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.