[SERVER-18878] FSM workloads with replication should be completed on secondary before next workload runs Created: 08/Jun/15 Updated: 05/Feb/16 Resolved: 12/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | CAP - 3.1.5 | ||||
| Participants: | |||||
| Description |
|
FSM workloads which run in replication, may still be running on a secondary after teardown has occurred on the primary. This means a subsequent workload may be impacted by a previous one. Additional protection during workload completion is required to ensure the workload has completed it's operations (insert document with write concern of all?). |
| Comments |
| Comment by Githook User [ 12/Jun/15 ] |
|
Author: {u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}Message: |