<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:39:33 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>[CSHARP-1422] MongoDB driver failed with writeconcern error</title>
                <link>https://jira.mongodb.org/browse/CSHARP-1422</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;We have deployed a replicated sharded cluster with 3 shards, each shard is a 3 member replica set(Primary,Secondary and Arbiter).&lt;br/&gt;
Also we are running 3 mongos and 3 config server instances. &lt;br/&gt;
We are importing data in this cluster form SQL server using .net service. This service uses MongoDB driver for .net. When we step down one of the primary, arbiter elects new primary and the cluster is up and running, but the MongoDB driver in the service waits for the write concern response from the previous primary, and gets timed out after some time. &lt;br/&gt;
Screen shot of the error from .net service is attached.&lt;/p&gt;

&lt;p&gt;MongoDB version is 3.0.6 and storage engine is wiredTiger&lt;/p&gt;</description>
                <environment>AWS</environment>
        <key id="231283">CSHARP-1422</key>
            <summary>MongoDB driver failed with writeconcern error</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</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="craig.wilson@mongodb.com">Craig Wilson</assignee>
                                    <reporter username="darshana.kedare@opussoft.com">darshana kedare</reporter>
                        <labels>
                            <label>question</label>
                    </labels>
                <created>Thu, 24 Sep 2015 10:08:13 +0000</created>
                <updated>Tue, 16 Nov 2021 13:18:14 +0000</updated>
                            <resolved>Mon, 28 Sep 2015 12:11:41 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="1044542" author="darshana.kedare@opussoft.com" created="Mon, 28 Sep 2015 03:59:31 +0000"  >&lt;p&gt;Thanks Craig&lt;br/&gt;
We will build the application with retry logic..&lt;/p&gt;

&lt;p&gt;Darshana&lt;/p&gt;</comment>
                            <comment id="1042268" author="craiggwilson" created="Thu, 24 Sep 2015 17:04:42 +0000"  >&lt;p&gt;Hi Darshana,&lt;/p&gt;

&lt;p&gt;Sorry you are having troubles. Just because MongoDB supports automatic failover does not mean you will not receive errors. Likely, what happened here is that a write was in process at the same time the failover was occurring. As such, you received a write concern error. It is your responsibility to handle an error like this and decide what to do with it. Either retry the operation or note in your logs somewhere for someone to follow-up on.&lt;/p&gt;

&lt;p&gt;Craig&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="91193" name="error.png" size="25808" author="darshana.kedare9389" created="Thu, 24 Sep 2015 10:08:13 +0000"/>
                    </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|hsdaxr:</customfieldvalue>

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