[DOCS-8942] fromMigrate flag never set for deletes in oplog Created: 28/Sep/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
|
When observing deletes was consolidated inside of mongo/db/catalog/collection.cpp, propagation of the fromMigrate flag was lost. This may affect third party tools that monitor the oplog to observe changes in replica sets, and expect the fromMigrate flag to be set in order to indicate operations that are logically internal to the sharded cluster. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Dianna Hohensee (Inactive) [ 29/Sep/16 ] |
|
This is internal and nothing a user should know about. ramon.fernandez, you set documentation needed on the original SERVER ticket. Do you agree? |