[JAVA-1514] Single Node Replica-set Write Concerns Created: 20/Oct/14 Updated: 11/Sep/19 Resolved: 23/Jun/15 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Configuration |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Steve Phillips | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
QA |
||
| Description |
|
In our QA environment, we use single-node replica-sets to simplify multi-environment deployments (QA, staging & prod all use replica-set configuration regardless of number of nodes) In our production environment, we would like to migrate from JOURNALLED to REPLICA_ACKNOWLEDGE. However, when using REPLICA_ACKNOWLEDGE with a single-node RS in our QA environments, write operations don't complete. We tried using tags and setting getLastErrorModes but that also failed. Is there a mechanism for using REPLICA-ACKNOWLEDGE with a single-node replica-set? |
| Comments |
| Comment by Ross Lawley [ 23/Oct/14 ] |
|
Hi stwaph, REPLICA_ACKNOWLEDGE is defined as:
So there is no mechanism for a single-node replica-set that would have the same write concern semantics for a multi node replicaset. Regarding QA we normally see either, an exact replica of the live system topology or a custom topology along with custom settings for that topology. Just a friendly reminder that either the mailing list or stackoverflow are the best resources for MongoDB behaviour type questions as they will reach a larger audience. The JAVA project is specifically for driver based bugs or issues. Regards, Ross |
| Comment by Steve Phillips [ 22/Oct/14 ] |
|
any update on this? |