<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 06:43:20 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>[SERVER-80363] server default writeConcern is not honored when wtimeout is set</title>
                <link>https://jira.mongodb.org/browse/SERVER-80363</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Sending &lt;tt&gt;wtimeout:x&lt;/tt&gt; without specifying &lt;tt&gt;w&lt;/tt&gt; value causes the server to use &lt;tt&gt;w:1, wtimeout:x&lt;/tt&gt; instead of combining wtimeout with server default (which should be majority in 5.0+).&lt;/p&gt;

&lt;p&gt;Reproduced with Java driver and mongo shell against 6.0.  In the logs it indicates it received only &lt;tt&gt;wtimeout:xxx&lt;/tt&gt; for writeConcern but it indicates it uses w:1 with passed wtimeout and claims it&apos;s provided by client.&lt;/p&gt;</description>
                <environment></environment>
        <key id="2424945">SERVER-80363</key>
            <summary>server default writeConcern is not honored when wtimeout is set</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</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="13201">Fixed</resolution>
                                        <assignee username="m.maher@mongodb.com">Moustafa Maher</assignee>
                                    <reporter username="asya.kamsky@mongodb.com">Asya Kamsky</reporter>
                        <labels>
                    </labels>
                <created>Wed, 23 Aug 2023 22:43:23 +0000</created>
                <updated>Mon, 5 Feb 2024 13:43:17 +0000</updated>
                            <resolved>Wed, 22 Nov 2023 01:58:11 +0000</resolved>
                                    <version>6.0.9</version>
                                    <fixVersion>7.2.1</fixVersion>
                    <fixVersion>7.3.0-rc0</fixVersion>
                    <fixVersion>7.0.5</fixVersion>
                                                        <votes>0</votes>
                                    <watches>18</watches>
                                                                                                                <comments>
                            <comment id="6009364" author="xgen-internal-githook" created="Sat, 13 Jan 2024 12:34:38 +0000"  >&lt;p&gt;Author: &lt;/p&gt;
{&apos;name&apos;: &apos;Moustafa Maher Khalil&apos;, &apos;email&apos;: &apos;m.maher@mongodb.com&apos;, &apos;username&apos;: &apos;moustafamaher&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-80363&quot; title=&quot;server default writeConcern is not honored when wtimeout is set&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-80363&quot;&gt;&lt;del&gt;SERVER-80363&lt;/del&gt;&lt;/a&gt; server default writeConcern is not honored when wtimeout is set&lt;br/&gt;
Branch: v7.2&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/6ebac6e589d809ba3425e66e37c767f14ac16f95&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/6ebac6e589d809ba3425e66e37c767f14ac16f95&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5927026" author="xgen-internal-githook" created="Tue, 5 Dec 2023 17:32:20 +0000"  >&lt;p&gt;Author: &lt;/p&gt;
{&apos;name&apos;: &apos;Moustafa Maher Khalil&apos;, &apos;email&apos;: &apos;m.maher@mongodb.com&apos;, &apos;username&apos;: &apos;moustafamaher&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-80363&quot; title=&quot;server default writeConcern is not honored when wtimeout is set&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-80363&quot;&gt;&lt;del&gt;SERVER-80363&lt;/del&gt;&lt;/a&gt; server default writeConcern is not honored when wtimeout is set&lt;/p&gt;

&lt;p&gt;(cherry picked from commit 8ecb0d8535cddd51f38e262ed2ff95105b4bd60a)&lt;/p&gt;

&lt;p&gt;GitOrigin-RevId: 9b61e09bb101b9992bfce99f98c6622f4c892057&lt;br/&gt;
Branch: v7.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/1684d02c4620f557ab9c721bad5ebbadb22d5337&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/1684d02c4620f557ab9c721bad5ebbadb22d5337&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5897210" author="xgen-internal-githook" created="Tue, 21 Nov 2023 23:41:34 +0000"  >&lt;p&gt;Author: &lt;/p&gt;
{&apos;name&apos;: &apos;Moustafa Maher Khalil&apos;, &apos;email&apos;: &apos;m.maher@mongodb.com&apos;, &apos;username&apos;: &apos;moustafamaher&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-80363&quot; title=&quot;server default writeConcern is not honored when wtimeout is set&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-80363&quot;&gt;&lt;del&gt;SERVER-80363&lt;/del&gt;&lt;/a&gt; server default writeConcern is not honored when wtimeout is set&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/8ecb0d8535cddd51f38e262ed2ff95105b4bd60a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/8ecb0d8535cddd51f38e262ed2ff95105b4bd60a&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5701783" author="samy.lanka" created="Wed, 13 Sep 2023 17:38:24 +0000"  >&lt;p&gt;I agree with Max. I think that educating customers about the missing fields makes more sense and will lead to a situation that will be easier to understand for customers (and for ourselves).&#160;&lt;/p&gt;</comment>
                            <comment id="5695325" author="JIRAUSER1257896" created="Mon, 11 Sep 2023 19:10:10 +0000"  >&lt;p&gt;I have discussed offline with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer@mongodb.com&quot;&gt;judah.schvimer@mongodb.com&lt;/a&gt; about my last suggestion about enforcing the w field and we agreed that is considered a breaking change to the stable API.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer@mongodb.com&quot;&gt;judah.schvimer@mongodb.com&lt;/a&gt; &amp;amp; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=samy.lanka%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;samy.lanka@mongodb.com&quot;&gt;samy.lanka@mongodb.com&lt;/a&gt; &amp;amp; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=asya.kamsky%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;asya.kamsky@mongodb.com&quot;&gt;asya.kamsky@mongodb.com&lt;/a&gt;&#160;&#160;are you agreeing with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn@mongodb.com&quot;&gt;max.hirschhorn@mongodb.com&lt;/a&gt; that we don&apos;t need to fix this but we can add some documentation to educate customers about the missing fields ?&#160;&lt;/p&gt;</comment>
                            <comment id="5691319" author="JIRAUSER1257896" created="Fri, 8 Sep 2023 23:25:41 +0000"  >&lt;p&gt;But I was thinking of an intermediate solution:&lt;br/&gt;
What do you think about the idea of enforcing that the writeConcern object must have &lt;b&gt;w field&lt;/b&gt; either in the commands or &lt;b&gt;CWWC&lt;/b&gt;, and that can easily being added through our IDL parsers ?&lt;br/&gt;
In my opinion that is more obvious and remove all ambiguity, with explaining the default values of missing fields.&#160;&lt;/p&gt;</comment>
                            <comment id="5691313" author="JIRAUSER1257896" created="Fri, 8 Sep 2023 23:17:16 +0000"  >&lt;p&gt;I&apos;ve been pondering the best way to tackle this issue, but every idea I come up (to stitch &lt;b&gt;WCs&lt;/b&gt; together) seems to make things more complicated&#160; which will make our documents even more ambiguous for users.&lt;br/&gt;
So I agree with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn@mongodb.com&quot;&gt;max.hirschhorn@mongodb.com&lt;/a&gt;, but yet we need to document the default values for missing fields that supplied by the client, or set in &lt;b&gt;CWWC&lt;/b&gt; which in this case &lt;b&gt;w:1.&lt;/b&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="5691299" author="max.hirschhorn@10gen.com" created="Fri, 8 Sep 2023 23:00:29 +0000"  >&lt;p&gt;Hello! I wanted to chime in here and make ensure I&apos;m understanding which type of application developers we are aiming to a solve a problem for.&lt;/p&gt;

&lt;p&gt;For example, I could imagine wanting to advertise - application developer sees &lt;a href=&quot;https://www.mongodb.com/blog/post/default-majority-write-concern-providing-stronger-durability-guarantees-out-box&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;MongoDB 5.0 provides a safe default write concern automatically&lt;/a&gt; and believes upon upgrade their application can immediately benefit. Is this user expectation reasonable? Possibly, but we also wrote text to say the new default won&apos;t override any explicit write concerns configured in the application itself. (Quoted inline below.)&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;b&gt;Upgrade considerations&lt;/b&gt;&lt;br/&gt;
For users who do not set any write concern and instead rely on the defaults that MongoDB provides, w:majority will become the default write concern starting in MongoDB 5.0. This new default will take effect without any user action.&lt;/p&gt;

&lt;p&gt;The new default &lt;b&gt;does not&lt;/b&gt; override any explicit write concerns that developers have configured previously. Developers who want their application to continue to use the write concern w:1 should explicitly set their default write concern to w:1 prior to upgrade, whether in their driver or server-side with a global write concern to maintain the previous behavior.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;So one question here may be - do application developers consider &lt;tt&gt;wtimeout&lt;/tt&gt; something different from an explicit write concern? In my mind, no, if the application constructs a WriteConcern object then its an explicit write concern. In most programming languages, auditing for usages of such a WriteConcern object is feasible with simple code search. I&apos;m open to hearing there being actual ambiguity from others on this ticket.&lt;/p&gt;

&lt;p&gt;If there is ambiguity, then is it specific to how &lt;tt&gt;wtimeout&lt;/tt&gt; combines with a cluster&amp;#45;wide default &lt;tt&gt;w&lt;/tt&gt; setting? My answer is yes.&lt;/p&gt;

&lt;p&gt;Let&apos;s say the situation was reversed slightly - The application code has explicitly constructed an operation with {writeConcern: {w: &quot;majority&quot;}}. And for one reason or another the cluster&amp;#45;wide default write concern is changed to be configured as {w: 2, wtimeout: 100} (yes, contrived I know). It would be a shock to me if the WriteConcern object expressed in the code was not one which actually took effect. That is, if the resulting write concern applied by the server was from combining the two settings into {writeConcern: {w: &quot;majority&quot;, wtimeout: 100}}. This would lead to a WriteConcernFailed error response being propagated if the secondaries are slightly lagged and not only when an election had occurred. This would result in application errors which while already possible to happen now possibly happening at a much higher frequency. Needing to type {writeConcern: {w: &quot;majority&quot;, wtimeout: 0}} to defensively guard against an operator configuring a bizarre cluster&amp;#45;wide default write concern feels very silly.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;We change that behaviour and try to fill all the missing fields of supplied writeConcern with the default write concern (or CWWC if exists)&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Filling in all of the missing fields of the supplied write concern is much more problematic to me. I&apos;m also not fully convinced layering client &lt;tt&gt;wtimeout&lt;/tt&gt; on top of cluster&amp;#45;wide &lt;tt&gt;w&lt;/tt&gt; is solving a common surprise in expectations. To me, the rule of &quot;if you type &apos;writeConcern&apos; in your application code then the cluster&amp;#45;wide default won&apos;t take effect&quot; satisfies the property of being simple to describe and doesn&apos;t sound unnatural.&lt;/p&gt;</comment>
                            <comment id="5658425" author="JIRAUSER1257896" created="Fri, 25 Aug 2023 04:07:37 +0000"  >&lt;p&gt;The complication is coming from multiple points:&lt;/p&gt;

&lt;p&gt;We used to identify that scenario as a &lt;b&gt;client-provided&lt;/b&gt; case, and within the code, there are several instances where the execution relies on the flag that specifies whether we utilize the &lt;b&gt;default&lt;/b&gt; setting or not. Therefore, it&apos;s necessary for us to assess whether we should consider an incompletely defined &lt;b&gt;writeConcern&lt;/b&gt; as coming from the client or as a default setting. This evaluation will have implications for the remaining code logic and the metrics that we have incorporated. Additionally, we must decide which absent fields we should populate using the default values.&lt;/p&gt;

&lt;p&gt;This decision-making process extends to determining whether to address only the &apos;&lt;b&gt;w&lt;/b&gt;&apos; parameter or should we also include the &apos;&lt;b&gt;wTimeout&lt;/b&gt;&apos; and &apos;&lt;b&gt;Journal&lt;/b&gt;&apos; options, among others. Furthermore, if we decide to allow incomplete write concerns, this implies permitting incomplete &apos;&lt;b&gt;CWWC&lt;/b&gt;&apos; as well. This could potentially result in a hybrid writeConcern configuration, an example being:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;{&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;   w: from implicit default,&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;   wTimout: from the client supplied,&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;   J: from CWWC&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;}&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;</comment>
                            <comment id="5658298" author="asya" created="Fri, 25 Aug 2023 01:21:12 +0000"  >&lt;p&gt;I think the current behavior is wrong aka bug for 5.0+ so I don&#8217;t think (1) is an option.  I&#8217;m a little surprised that (2) is complicated given we are already setting an arbitrary default but I suppose just changing it to majority starting in 5.0 is technically incorrect for clusters that changed their default WC to something else.  &lt;/p&gt;

&lt;p&gt;Given how long this has been broken I guess it&#8217;s ok not to hold up 7.1 for it, but I feel strongly we should fix and backport this soon. &lt;/p&gt;</comment>
                            <comment id="5657963" author="JIRAUSER1257896" created="Thu, 24 Aug 2023 22:22:13 +0000"  >&lt;p&gt;I agree with you &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer@mongodb.com&quot;&gt;judah.schvimer@mongodb.com&lt;/a&gt;, So I should put this ticket back to scheduling and not block 7.1 on it, do you agree ?&lt;/p&gt;</comment>
                            <comment id="5657955" author="judah.schvimer" created="Thu, 24 Aug 2023 22:18:11 +0000"  >&lt;p&gt;I think (2) is a lot more intuitive to me, but we can defer the backport decision to after we&apos;ve completed the fix on master.&lt;/p&gt;</comment>
                            <comment id="5657914" author="JIRAUSER1257896" created="Thu, 24 Aug 2023 21:51:24 +0000"  >&lt;p&gt;I have investigating this, and I see that is working as design since &lt;b&gt;v4.2&lt;/b&gt;, that if the client specify any write concern (like in this ticket &quot;&lt;em&gt;&lt;b&gt;writeConcern&quot;: {&quot;wtimeout&quot;:10000}&lt;/b&gt;&quot;&lt;/em&gt;&#160;we &lt;a href=&quot;https://github.com/mongodb/mongo/blob/aed3561d4cf3463e78801ef73fbf563919b1397c/src/mongo/db/write_concern_options.cpp#L198&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;won&apos;t use the &lt;/a&gt;cluster wide write concern (CWWC) and treat it as client supplied write concern and let the IDL parser to parse it and default all missing fields to its default values which is &lt;b&gt;1&lt;/b&gt; for the field &lt;b&gt;w&lt;/b&gt;.&lt;br/&gt;
So when we introduced the &lt;b&gt;implicitMajorityDefaultWC project&lt;/b&gt; to set the default wc to &lt;b&gt;majority&lt;/b&gt; if CWWC doesn&apos;t exist we honoured the existent behaviour of of the client supplied write concern.&lt;/p&gt;

&lt;p&gt;&lt;ins&gt;That being said, we have two options:&lt;/ins&gt;&#160;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;We edit our documentation to reflect that behaviour.
	&lt;ul&gt;
		&lt;li&gt;Easier solution.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;We change that behaviour and try to fill all the missing fields of supplied writeConcern with the default write concern (or CWWC if exists) but that will be a bit complex change and risky change to &lt;b&gt;block 7.1&lt;/b&gt; for it.
	&lt;ul&gt;
		&lt;li&gt;In my opinion I see this area of the code is complex and we need to fix it and remove this ambiguity.&lt;/li&gt;
		&lt;li&gt;But I think backporting this to 5.0 will be complex as I see alot of changes made around that area since. (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-62609&quot; title=&quot;WriteConcernOptions should use the WriteConcernW type&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-62609&quot;&gt;&lt;del&gt;SERVER-62609&lt;/del&gt;&lt;/a&gt;)&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer@mongodb.com&quot;&gt;judah.schvimer@mongodb.com&lt;/a&gt; &amp;amp; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=samy.lanka%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;samy.lanka@mongodb.com&quot;&gt;samy.lanka@mongodb.com&lt;/a&gt; what do you think ?&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10420">
                    <name>Backports</name>
                                            <outwardlinks description="backported by">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="2498679">SERVER-83193</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2319842">SERVER-76351</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                                                <inwardlinks description="is documented by">
                                        <issuelink>
            <issuekey id="2506995">DOCS-16510</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10520">
                    <name>Problem/Incident</name>
                                            <outwardlinks description="causes">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="2564920">SERVER-86116</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2566714">SERVER-86201</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="563928">DRIVERS-2074</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>13.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="25128"><![CDATA[Replication]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12450" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Backport Requested</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="26553"><![CDATA[v7.2]]></customfieldvalue>
    <customfieldvalue key="25578"><![CDATA[v7.0]]></customfieldvalue>
    <customfieldvalue key="23470"><![CDATA[v6.0]]></customfieldvalue>
    <customfieldvalue key="21777"><![CDATA[v5.0]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10011"><![CDATA[Minor Change]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5006R00001vg8xUQAQ]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 23 Aug 2023 22:55:58 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        3 weeks, 4 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_17052" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Downstream Changes Summary</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>- Explicitly documenting that missing &amp;#39;w&amp;#39; field from write concern object will be filled with default write concern.&lt;br/&gt;
&lt;br/&gt;
- &amp;#39;w&amp;#39; field is not optional while setting default write concern using setDefaultRWConcern command </customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_17050" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Downstream Team Attention</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16942"><![CDATA[Needed]]></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>paolo.polato@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            3 weeks, 4 days ago
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_16465" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Linked BF Score</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10026"><![CDATA[ALL]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>asya.kamsky@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>judah.schvimer@mongodb.com</customfieldvalue>
            <customfieldvalue>max.hirschhorn@mongodb.com</customfieldvalue>
            <customfieldvalue>m.maher@mongodb.com</customfieldvalue>
            <customfieldvalue>samy.lanka@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i2nl5j:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|i25m88:</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_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_22250" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Special Downgrade Instructions Required</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="23343"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="7776">Repl 2023-09-18</customfieldvalue>
    <customfieldvalue id="7777">Repl 2023-10-02</customfieldvalue>
    <customfieldvalue id="7778">Repl 2023-10-16</customfieldvalue>
    <customfieldvalue id="7877">Repl 2023-10-30</customfieldvalue>
    <customfieldvalue id="7878">Repl 2023-11-13</customfieldvalue>
    <customfieldvalue id="7879">Repl 2023-11-27</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_17051" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Teams Impacted</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16944"><![CDATA[Docs]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i2n7av:</customfieldvalue>

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