[SERVER-14483] Unit test awaitReplication behavior across reconfig Created: 07/Jul/14 Updated: 02/Aug/18 Resolved: 04/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
If a client is awaiting replication for a specific write concern to be satisfied and the set gets reconfigured, awaitReplication should begin considering satisfaction based on the new configuration. It should also detect if under the new configuration the criteria are unsatisfiable, and return an error if so. This task is to write unit tests of the replication coordinator to validate this behavior. |
| Comments |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |