There are a few places where we log or return an error message when a sharded collection's epoch changes that assume the collection was dropped and recreated (e.g. here). Previously this was correct, but as of 4.4 refining a collection's shard key can also change the epoch, so such messages/logs are misleading and should be updated.
Error messages and logging should not assume collection was dropped and recreated on epoch change
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: