[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:
Related
Assigned Teams:
Replication
Participants:
Case:

 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:

 WARNING: the collection 'foo.tmp.bar' lacks a unique index on _id. This index is needed for replication to function properly

Since this collection is never going to be replicated (temporary mr collection - SERVER-13981) there should not be a warning about it not being able to replicate properly



 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.

Generated at Thu Feb 08 03:49:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.