[SERVER-21412] Record temp collection drops to oplog when becoming primary Created: 11/Nov/15 Updated: 23/Jan/17 Resolved: 23/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2017-02-13 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In order to better cleanup temp collection in the whole replica set, record their drop on the primary, into the oplog. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 23/Dec/16 ] |
|
Confirmed that the current behavior does indeed already record the drops to the collection. |
| Comment by Spencer Brody (Inactive) [ 18/Nov/16 ] |
|
Judah, can you investigate what the current behavior is? Last we discussed this we believed this was actually already happening. |
| Comment by Eric Milkie [ 21/Dec/15 ] |
|
Are we ever dropping any replicated temp collections when stepping up to primary, or are we only dropping non-replicated temp collections? |