<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:12:35 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>[DOCS-15321] Document that writeConcern.wtimeout is not applicable to sharded cluster ddl operations</title>
                <link>https://jira.mongodb.org/browse/DOCS-15321</link>
                <project id="10380" key="DOCS">Documentation</project>
                    <description>&lt;p&gt;In &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-65340&quot; title=&quot;Operations hang when re-using dropped unsharded collections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-65340&quot;&gt;&lt;del&gt;SERVER-65340&lt;/del&gt;&lt;/a&gt;, we are discussing that if a sharded cluster performing a rename operation reaches a point where it cannot roll back a rename operation, it&apos;s going to continue retrying indefinitely. So, writeConcern.wtimeout should not be provided to a renameCollection in a sharded cluster.&lt;/p&gt;

&lt;p&gt;We can make this behavior clearer:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://www.mongodb.com/docs/manual/reference/command/renameCollection/#resource-locking-in-sharded-clusters&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;and in the writeConcern field description &lt;a href=&quot;https://www.mongodb.com/docs/manual/reference/command/renameCollection/#mongodb-dbcommand-dbcmd.renameCollection&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Additionally:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&quot;Resource locking in sharded clusters&quot; could be clarified to include reference to majority write concern, as is described in the writeConcern field description&lt;/li&gt;
	&lt;li&gt;There may be other operations that should be similarly clarified (cc &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=pierlauro.sciarelli%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;pierlauro.sciarelli@mongodb.com&quot;&gt;pierlauro.sciarelli@mongodb.com&lt;/a&gt; can you suggest others?)&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="2039906">DOCS-15321</key>
            <summary>Document that writeConcern.wtimeout is not applicable to sharded cluster ddl operations</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="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="eric.sedor@mongodb.com">Eric Sedor</reporter>
                        <labels>
                            <label>backlog</label>
                            <label>feature</label>
                            <label>replication</label>
                            <label>sharding</label>
                    </labels>
                <created>Wed, 4 May 2022 21:34:50 +0000</created>
                <updated>Mon, 22 Jan 2024 16:13:02 +0000</updated>
                                                                            <component>manual</component>
                    <component>Server</component>
                        <due></due>
                            <votes>1</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="4528786" author="tommaso.tocci" created="Thu, 5 May 2022 15:27:13 +0000"  >&lt;p&gt;We should also change:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://www.mongodb.com/docs/manual/reference/command/setDefaultRWConcern/#sharding-administrative-commands-override-write-concern-settings&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.mongodb.com/docs/manual/reference/command/setDefaultRWConcern/#sharding-administrative-commands-override-write-concern-settings&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In fact DDL operation in sharded clsuter do not use write concern timeout at all. Once they start they are guaranteed to complete eventually&lt;/p&gt;</comment>
                            <comment id="4528014" author="tommaso.tocci" created="Thu, 5 May 2022 10:42:15 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=pierlauro.sciarelli%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;pierlauro.sciarelli@mongodb.com&quot;&gt;pierlauro.sciarelli@mongodb.com&lt;/a&gt; for the clarification. I just wanted to summarize briefly the relation between Sharded DDL operations and WriteConcern:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;All sharded DDL operations must be invoked with majority writeConcern, otherwise they will simply return an InvalidOptions error.&lt;/li&gt;
	&lt;li&gt;All sharded DDL operations ignore the given writeConcern timeout.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="4527919" author="pierlauro.sciarelli" created="Thu, 5 May 2022 09:48:26 +0000"  >&lt;p&gt;While write concerns for DDLs can be used in replica sets, no write concern other than majority may be provided for sharded DDLs. I would try to explicitly point that out in the documentation: metadata operations are not transactional within a sharded cluster (each shard independently executes them), so once they all start they&apos;re all expected to finish (and that is &lt;ins&gt;guaranteed&lt;/ins&gt; to happen for every DDL operations as soon as all shards can majority commit). The rationale behind that is: if there is no possibility to majority commit in a sharded cluster, the user better solve that because anyway all data operations may be rollback-ed at some point.&lt;/p&gt;

&lt;p&gt;Regarding the wtimeout, there seems to have been a lot of confusion regarding it in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-65340&quot; title=&quot;Operations hang when re-using dropped unsharded collections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-65340&quot;&gt;&lt;del&gt;SERVER-65340&lt;/del&gt;&lt;/a&gt;: the &quot;problem&quot; (that is arguably a problem since the cluster self-recovers when majority commit is available) is reproducible also without setting &lt;tt&gt;wtimeout&lt;/tt&gt;. And - in general - if a timeout is hit it does not necessarily mean that the operation failed, as also stated by &lt;a href=&quot;https://www.mongodb.com/docs/manual/reference/write-concern/#wtimeout&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;the documentation&lt;/a&gt;: &quot;MongoDB does not undo successful data modifications performed before the write concern exceeded the wtimeout time limit&quot;.&lt;/p&gt;

&lt;p&gt;A questions may arise at this point: why are we allowing write concerns to be set for sharded DDLs? Since applications need to work seamlessly both on plain replica sets and sharded clusters, the public APIs are still allowing users to set write concerns. Any set write concern is then ignored and &quot;upgraded&quot; always to majority in a sharded cluster. (NB: this only applies to DDLs, write concerns are always respected for CRUD operations).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="2019582">SERVER-65340</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 5 May 2022 09:48:26 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        1 year, 39 weeks, 6 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>DOCSP-11702</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>emet.ozar@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            1 year, 39 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>eric.sedor@mongodb.com</customfieldvalue>
            <customfieldvalue>pierlauro.sciarelli@mongodb.com</customfieldvalue>
            <customfieldvalue>tommaso.tocci@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i0tq2v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|i0cn7s:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i0tc87:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                </customfields>
    </item>
</channel>
</rss>