-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.4.23
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Execution Team 2024-02-05
In 4.4, removing index keys from a unique partial index that do not satisfy the partial filter may generate write conflicts for concurrent storage transactions that are also removing unindexed entries. This is largely due to existing logic intended to work with pre-4.2 background indexing operations, which is no longer a concern since background index builds were deprecated by hybrid index builds in 4.2.
Some of this write conflicting behavior was removed in 5.0 as part of the cleanup in SERVER-51762.
Prior to 4.4.23 (and SERVER-75922), this write conflicting behavior did not exist because we would return early on a partial filter miss.
- is related to
-
SERVER-28546 Documents can erroneously be unindexed from a partial index
- Closed
-
SERVER-75922 Partial unique indexes created on MongoDB 4.0 can be missing index keys after upgrade to 4.2 and later, leading to uniqueness violations
- Closed
-
SERVER-39471 Remove unique index FCV upgrade codepath
- Closed
-
SERVER-51762 Delete code for old unique index format
- Closed
-
SERVER-85670 Test for unique partial index write conflicts
- Closed