[SERVER-43372] Move CryptDReplicationCoordinatorNoOp from enterprise to community repo Created: 18/Sep/19 Updated: 29/Oct/23 Resolved: 23/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Repl 2019-09-23 | ||||
| Participants: | |||||
| Description |
|
For For Let's move CryptDReplicationCoordinatorNoOp into the community code base and rename it ReplicationCoordinatorNoOp, so we can change it in sync with ReplicationCoordinator. Code in the enterprise module can still use the NoOp class (only for instantiating it), but changes in that class won't affect the enterprise code, since it doesn't explicitly call any of its methods. |
| Comments |
| Comment by Githook User [ 24/Sep/19 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: |
| Comment by Githook User [ 24/Sep/19 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: |
| Comment by A. Jesse Jiryu Davis [ 23/Sep/19 ] |
|
Requesting backport to 4.2, since PM-1400 "Reduce Client Time To Recovery On Topology Changes" will require ReplicationCoordinator interface changes and we intend to backport some of that work. If desired we can leave the backport unscheduled until we're sure about backporting the dependent work in PM-1400. |
| Comment by Githook User [ 23/Sep/19 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}Message: |