[SERVER-44924] Misleading "collection dropped or recreated" log message on secondary refreshes Created: 03/Dec/19 Updated: 27/Oct/23 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Josef Ahmad | Assignee: | Allison Easton |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng, sharding-interns-2020 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
A StaleConfig event on a shard secondary reads "the collection may have been dropped and recreated" for the most common and recurring case of a metadata refresh of an existing collection (here). This can mislead the observer. |
| Comments |
| Comment by Carl Champain (Inactive) [ 03/Dec/19 ] |
|
Hi josef.ahmad, Passing this ticket along to the Sharding team. |