[SERVER-7328] enhanced replica set repair process Created: 11/Oct/12  Updated: 06/Dec/22  Resolved: 14/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.2.0
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Scott D Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

While bringing new nodes into a replica set or compacting existing nodes the cluster is aware that the node is "recovering" and the status reflects it. What's more: it doesn't cause a warning message in the log files every two seconds. It would be nice to have the cluster aware of the ongoing repair process.

I would also like to see it possible for when a node finishes the repair, it immediately joins back into the cluster and carries on working as normal.

A third feature would be to issue a warning or error if there doesn't appear to be enough space for a repair to even take place (though I understand this isn't so cut and dry).

The motivation behind these requests are to make the repair process a bit easier to automate and leave running without someone staring at it: something that you can just fire and forget on a cluster node over a weekend, for example.



 Comments   
Comment by Spencer Brody (Inactive) [ 14/Jun/18 ]

This isn't a complaint we've heard much in the years since this ticket was filed.  Closing this for now, if it comes up again we can reassess.

Generated at Thu Feb 08 03:14:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.