[SERVER-23304] Arbiters should drop non-repl data at startup Created: 23/Mar/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
If there is non-system (replset/log) data it should be dropped at startup. If not, things like authentication can work differently than other members. Note: It might be better to simply disallow (local) access to that data rather than dropping it. Remote queries will already be disabled due to replication role, !isMaster. |
| Comments |
| Comment by Eric Milkie [ 08/Sep/16 ] |
|
Or perhaps we should simply refuse to transition to ARBITER state if there is data. I don't particularly like the idea of dropping the data. |