fle2 cleanup/compact can fail with a WriteConflict exception due to concurrent catalog changes on the fle2 auxiliary collection. This is because the cleanup/compact implementation performs two distinct set of ShardRole collection acquisitions (1 and 2). The first one will open a storage snapshot and snapshot the catalog. The second acquisition then expects to observe the latest instance of the auxiliary collections, but in might happen that the stashed catalog does not report the latest version when a concurrent operation has made a change to them.
- is caused by
-
SERVER-103398 Investigate usage validity of CollectionPtr::CollectionPtr_UNSAFE
-
- Closed
-