Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
3.2.0, 3.3.3
-
None
-
Replication
-
Fully Compatible
-
ALL
Description
Transitioning from removed->arbiter or from arbiter->removed->??? should error/fassert until those transitions are coded and tested (=supported).
Odd things will happen if this is allowed, like replication of data continues on an arbiter, until restarted.
Attachments
Issue Links
- is related to
-
SERVER-23304 Arbiters should drop non-repl data at startup
-
- Backlog
-
- related to
-
SERVER-27953 Improve error message when removing a node from a replica set and re-adding it as an arbiter
-
- Backlog
-