-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v6.1, v6.0
-
Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31
The shardCollection command may drop the collection if there's a stepDown while it is running. Currently, this results in a drop collection event in change stream even though the collection isn't dropped from the user's perspective. I think if this drop is marked as fromMigrate: true, then it will skipped by change stream. And I think this is a more correct behavior.
With this spurious drop, it is very difficult/confusing for downstream to use change streams.
- causes
-
SERVER-71880 _shardsvrDropCollectionParticipant with fromMigrate=true does not abort index builds
- Closed
-
SERVER-72235 Avoid the usage of dropCollectionEvenIfSystem() outside of resharding code
- Closed