[SERVER-8563] Use two threads and be able to manage them for replica set replication Created: 14/Feb/13  Updated: 08/Mar/13  Resolved: 05/Mar/13

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

Type: New Feature Priority: Major - P3
Reporter: Mark Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

any


Participants:

 Description   

Cause for this ticket.
I had a secondary which would crash on duplicate key indexes when it rejoined a replica set. It didn't make any sense. I would like more control over the replica set itself in terms of how it works.

Two threads:
a. A download thread to be executed.
b. A thread executing the commands downloaded.

In any case, it would be nice to have two threads doing the following:
1. You can stop and start any of the threads.
2. You can skip a command if a thread stops executing.
3. When the execute thread dies tor stops, an option to just have it stop being part of a replica set — but not to let it crash.
4. Continue to execute the commands downloaded even if disconnected from the replica set upto the last known good point in the replica set.



 Comments   
Comment by Eric Milkie [ 05/Mar/13 ]

The current design of replication precludes most of the described behaviors. There are some hooks to control replication behavior, but these are only available to unit tests.

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