-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance, Write Ops
-
None
-
ALL
As part of SERVER-3067, foreground index builds were made interruptable, but only for user-initiated builds. System-initiated builds were not made interruptable, because we suspected that the code was not prepared to gracefully handle this type of failure. We determined whether an operation was from a user by looking at whether the CurOp was nested or not. Nesting occurs when a DBDirectClient is in use.
When we added support for Write Commands, the support also utilized this wrapping ability of CurOp. This may not be aggregating the correct operation stats, in addition to breaking index build interruptibility.
Tests forthcoming.
- duplicates
-
SERVER-12139 fix performance regression of batch inserts via write commands
- Closed
- is related to
-
SERVER-3067 Can't kill indexing operations
- Closed
-
SERVER-11767 creating background index and then dropping doesn't seem to cancel background build on secondary
- Closed