<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:54:48 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[JAVA-1514] Single Node Replica-set Write Concerns</title>
                <link>https://jira.mongodb.org/browse/JAVA-1514</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;In our QA environment, we use single-node replica-sets to simplify multi-environment deployments (QA, staging &amp;amp; prod all use replica-set configuration regardless of number of nodes)&lt;/p&gt;

&lt;p&gt;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&apos;t complete.  We tried using tags and setting getLastErrorModes but that also failed.&lt;/p&gt;

&lt;p&gt;Is there a mechanism for using REPLICA-ACKNOWLEDGE with a single-node replica-set?&lt;/p&gt;</description>
                <environment>QA</environment>
        <key id="164582">JAVA-1514</key>
            <summary>Single Node Replica-set Write Concerns</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="stwaph">Steve Phillips</reporter>
                        <labels>
                    </labels>
                <created>Mon, 20 Oct 2014 20:22:59 +0000</created>
                <updated>Wed, 11 Sep 2019 19:11:34 +0000</updated>
                            <resolved>Tue, 23 Jun 2015 15:40:12 +0000</resolved>
                                                                    <component>Configuration</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="747754" author="ross@10gen.com" created="Thu, 23 Oct 2014 14:21:23 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=stwaph&quot; class=&quot;user-hover&quot; rel=&quot;stwaph&quot;&gt;stwaph&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;REPLICA_ACKNOWLEDGE&lt;/tt&gt; is &lt;a href=&quot;http://docs.mongodb.org/manual/core/write-concern/#replica-set-write-concern&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;defined&lt;/a&gt; as:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;(a) write operation to a replica set with write concern level of w:2 or write to the primary and at least one secondary.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Just a friendly reminder that either the &lt;a href=&quot;https://groups.google.com/group/mongodb-user&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mailing list&lt;/a&gt; or &lt;a href=&quot;http://stackoverflow.com/questions/tagged/mongodb&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;stackoverflow&lt;/a&gt; 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.&lt;/p&gt;

&lt;p&gt;Regards,&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                            <comment id="746919" author="stwaph" created="Wed, 22 Oct 2014 03:58:17 +0000"  >&lt;p&gt;any update on this?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hs37y7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>143624</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>