[SERVER-18937] Don't raise startup warnings on missing _id for collections that don't get replicated Created: 11/Jun/15 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andre de Frere | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
It is possible for a map/reduce job to be interrupted in such a way that the _id does not exist. When a node with this issue is restarted, a message similar to the following will appear in startup warnings:
Since this collection is never going to be replicated (temporary mr collection - |
| Comments |
| Comment by Eric Milkie [ 12/Jun/15 ] |
|
It might be the case that at startup, we do the tmp-collection cleanup phase after we do the missing _id detection phase. So if we swapped the order, that would fix this issue. |