[SERVER-27953] Improve error message when removing a node from a replica set and re-adding it as an arbiter Created: 08/Feb/17  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.1
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Geert Hendrickx Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 1
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File assert.txt    
Issue Links:
Related
is related to SERVER-23303 Do not allow transition to/from Arbit... Backlog
Assigned Teams:
Replication
Participants:

 Description   

Currently you get an OplogOutOfOrder fassert with a stack trace. Instead we should be able to detect that the node was changed to/from arbiter status and log a message that mentions that and fasserts without a stack trace.



 Comments   
Comment by Spencer Brody (Inactive) [ 13/Feb/17 ]

Changing a node to/from arbiter requires restarting the node and removing the data directory, as is documented here.

It is true that the error message could be clearer in this case, I'm going to change this ticket to be about cleaning up the logging when this happens, but the procedure to correctly change a node to be an arbiter will be unchanged.

Generated at Thu Feb 08 04:16:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.