[DOCS-13430] Investigate changes in SERVER-46122: Make the drop command abort in-progress index builds Created: 19/Feb/20  Updated: 13/Nov/23  Resolved: 06/Mar/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.4, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-46122 Make the drop command abort in-progre... Closed
Participants:
Days since reply: 3 years, 48 weeks, 5 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

The "drop" command now aborts in-progress index builds before dropping any ready indexes or the collection itself. Previously, if there were any in-progress index, the command would return the "BackgroundOperationInProgressForNamespace" error code.

Description of Linked Ticket

While dropping a collection, it should abort any in-progress index builds.

Aborting the index will produce an abortIndexBuilds oplog entry, which suffices for in-progress index builds when dropping the collection. Secondaries should not abort in-progress index builds but instead wait for the abortIndexBuilds oplog entry.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 06/Mar/20 ]

Author:

{'name': 'jeff-allen-mongo', 'username': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com'}

Message: (DOCS-13430): drop() aborts in-progress index builds
Branch: master
https://github.com/mongodb/docs/commit/9fa893b116d542d5f43f067d416feb5c4a514782

Generated at Thu Feb 08 08:07:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.