[SERVER-23767] Replace DataReplicator's use of ReplicationExecutor with ThreadPoolExecutor Created: 15/Apr/16 Updated: 19/Jul/16 Resolved: 18/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Benety Goh |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 18 (08/05/16) | ||||||||
| Participants: | |||||||||
| Description |
|
We can use a ThreadPoolTaskExecutor + helper classes to make a nice interface to create the OperationContext and take DB/Coll locks for the callers lambda. All internal state will need to be protected by the DataReplicator internal mutex, as is done mostly already. |
| Comments |
| Comment by Benety Goh [ 18/Jul/16 ] |
|
Fixed in: Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |