<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:57:59 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-41532] Mongos can fail with &quot;a non-retryable snapshot error&quot; and &quot;Unable to read from a snapshot due to pending collection catalog changes&quot;</title>
                <link>https://jira.mongodb.org/browse/SERVER-41532</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;The full error message is:&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;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: blue; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;&quot;Command insert failed: Transaction 3a15840d-e673-4fb1-b4a8-dad5bef4231f:1 was aborted on statement 0 due to: a non-retryable snapshot error :: caused by :: Encountered error from localhost:27019 during a transaction :: caused by :: Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1559738408, 3). Collection minimum is Timestamp(1559738412, 8).&quot;&lt;/span&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;
&lt;p&gt;The error message suggests retrying the operation, and in fact the operation DOES succeed after a retry.&lt;/p&gt;

&lt;p&gt;However, this seems like an unnecessary error to return to the application.&lt;/p&gt;

&lt;p&gt;The server should just block until the pending collection catalog changes have been completed and then execute the operation without error.&lt;/p&gt;</description>
                <environment></environment>
        <key id="789867">SERVER-41532</key>
            <summary>Mongos can fail with &quot;a non-retryable snapshot error&quot; and &quot;Unable to read from a snapshot due to pending collection catalog changes&quot;</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="3">Duplicate</resolution>
                                        <assignee username="randolph@mongodb.com">Randolph Tan</assignee>
                                    <reporter username="robert@mongodb.com">Robert Stam</reporter>
                        <labels>
                            <label>sharding-wfbf-day</label>
                    </labels>
                <created>Wed, 5 Jun 2019 13:11:23 +0000</created>
                <updated>Tue, 22 Feb 2022 22:03:22 +0000</updated>
                            <resolved>Thu, 16 Apr 2020 18:48:34 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>12</watches>
                                                                                                                <comments>
                            <comment id="3687499" author="JIRAUSER1259186" created="Sat, 27 Mar 2021 05:34:18 +0000"  >&lt;p&gt;I&#160; also have this problem, I first create a table, then insert a data, sleep 1s, open the transaction transaction insert data is still wrong&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;mongd single node 4.2.6 replica-set&lt;/p&gt;</comment>
                            <comment id="2913069" author="dianna.hohensee" created="Wed, 26 Feb 2020 21:23:04 +0000"  >&lt;p&gt;Looking at the v4.3 and v4.2 code, we consistently return a SnapshotUnavailable error on the mongod whenever this happens. The mongod cannot retry on its own with a newer timestamp because it&apos;s a snapshot readConcern at a time selected by the mongos for all shards. Part of the msg included in the ticket description says &quot;non-retryable snapshot error&quot;. I&apos;m unsure whether this is the current state of the code, or old state of the code. Oleg&apos;s most recent comment with a log message does not have &quot;non-retryable snapshot error&quot;.&lt;/p&gt;

&lt;p&gt;Options:&lt;br/&gt;
1) SnapshotUnavailable should be a user retryable error, if it isn&apos;t today.&lt;br/&gt;
2) Mongos should forward the error code, if it isn&apos;t already.&lt;br/&gt;
3) Mongos should retry internally on this error from mongod servers.&lt;/p&gt;

&lt;p&gt;The in-memory catalog is not multi-versioned, so we cannot do anything right now to stop the error from happening when a read comes in at a time earlier than the most modification of that collection. Since the recent modification of the collection was creating it, even in a multi-version in-memory catalog world, the insert is not going to find a collection at that point-in-time, and I doubt we&apos;ll create the collection at that time since the collection already exists (hypothetical hand-wavy...).&lt;/p&gt;</comment>
                            <comment id="2905393" author="dianna.hohensee" created="Mon, 24 Feb 2020 18:16:44 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=oleg.pudeyev&quot; class=&quot;user-hover&quot; rel=&quot;oleg.pudeyev&quot;&gt;oleg.pudeyev&lt;/a&gt; My first thought is that the cluster time of the mongos used to route the insert request is stale relative to the mongod targeted for the insert. I believe &apos;snapshot&apos; read concern means that the mongos picks a time at which to read, which is the mongos&apos; cluster time, and then the request forwarded to the mongod will be to open a snapshot at that selected time.&lt;/p&gt;

&lt;p&gt;So I can see the test failing if the create goes through mongos1, pushing the cluster time forward for mongos1 and mongod1; and then the insert goes through mongos2, getting an old cluster time, and reaching mongod1 with a too-old timestamp.&lt;/p&gt;</comment>
                            <comment id="2337561" author="xgen-internal-githook" created="Mon, 22 Jul 2019 20:55:31 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Oleg Pudeyev&apos;, &apos;email&apos;: &apos;39304720+p-mongo@users.noreply.github.com&apos;, &apos;username&apos;: &apos;p-mongo&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1855&quot; title=&quot;Run all transaction tests on sharded clusters&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1855&quot;&gt;&lt;del&gt;RUBY-1855&lt;/del&gt;&lt;/a&gt; run transaction api tests on sharded topologies (#1455)&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1855&quot; title=&quot;Run all transaction tests on sharded clusters&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1855&quot;&gt;&lt;del&gt;RUBY-1855&lt;/del&gt;&lt;/a&gt; run transaction api tests on sharded topologies&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1868&quot; title=&quot;Reduce non-determinism in the whole of ruby test suite&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1868&quot;&gt;&lt;del&gt;RUBY-1868&lt;/del&gt;&lt;/a&gt; improve diagnostics when spec tests fail&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Improve crud spec tests event diagnostics&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;skip failing tests due to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-41532&quot; title=&quot;Mongos can fail with &amp;quot;a non-retryable snapshot error&amp;quot; and &amp;quot;Unable to read from a snapshot due to pending collection catalog changes&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-41532&quot;&gt;&lt;del&gt;SERVER-41532&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: 2.10-stable&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-ruby-driver/commit/5a19b26ef90275aea077bdec2f33847bb7d616e4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-ruby-driver/commit/5a19b26ef90275aea077bdec2f33847bb7d616e4&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="2336696" author="xgen-internal-githook" created="Mon, 22 Jul 2019 15:25:04 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Oleg Pudeyev&apos;, &apos;email&apos;: &apos;39304720+p-mongo@users.noreply.github.com&apos;, &apos;username&apos;: &apos;p-mongo&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1855&quot; title=&quot;Run all transaction tests on sharded clusters&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1855&quot;&gt;&lt;del&gt;RUBY-1855&lt;/del&gt;&lt;/a&gt; run transaction api tests on sharded topologies (#1455)&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1855&quot; title=&quot;Run all transaction tests on sharded clusters&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1855&quot;&gt;&lt;del&gt;RUBY-1855&lt;/del&gt;&lt;/a&gt; run transaction api tests on sharded topologies&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/RUBY-1868&quot; title=&quot;Reduce non-determinism in the whole of ruby test suite&quot; class=&quot;issue-link&quot; data-issue-key=&quot;RUBY-1868&quot;&gt;&lt;del&gt;RUBY-1868&lt;/del&gt;&lt;/a&gt; improve diagnostics when spec tests fail&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Improve crud spec tests event diagnostics&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;skip failing tests due to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-41532&quot; title=&quot;Mongos can fail with &amp;quot;a non-retryable snapshot error&amp;quot; and &amp;quot;Unable to read from a snapshot due to pending collection catalog changes&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-41532&quot;&gt;&lt;del&gt;SERVER-41532&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-ruby-driver/commit/a9193c223ef56ed615b4be2ab7a7d4b525cd3e76&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-ruby-driver/commit/a9193c223ef56ed615b4be2ab7a7d4b525cd3e76&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="2335091" author="oleg.pudeyev" created="Fri, 19 Jul 2019 22:52:25 +0000"  >&lt;p&gt;I am getting this error in about 50% of the test runs of this test on 4.2 and 4.3 sharded: &lt;a href=&quot;https://github.com/mongodb/specifications/blob/master/source/transactions-convenient-api/tests/transaction-options.yml&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/specifications/blob/master/source/transactions-convenient-api/tests/transaction-options.yml&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Note that this test&apos;s set up arranges for an empty collection (we drop and create the collection with w: majority), and the operations are inserts. On the third or fourth test of a single run, I get this:&lt;/p&gt;

&lt;p&gt;#&amp;lt;Mongo::Error::OperationFailure: Transaction 0560f3da-5f70-4582-927a-890c45fa2126:1 was aborted on statement 0 due to: a non-retryable snapshot error :: caused by :: Encountered error from localhost:14442 during a transaction :: caused by :: Unable to read from a snapshot due to pending collection catalog changes; please retry the operation. Snapshot timestamp is Timestamp(1563576172, 39). Collection minimum is Timestamp(1563576172, 47) (246)&amp;gt;&lt;/p&gt;

&lt;p&gt;In about half the cases, this error doesn&apos;t happen and the entire run succeeds.&lt;/p&gt;

&lt;p&gt;I tried, as a workaround, to insert and delete some data using the transaction api helper (which does retry), thus forcing the error to happen during the setup phase where the operation can be retried, but I have not succeeded - the inserts in the setup never fail but the actual insert in the test still fails (half the time).&lt;/p&gt;

&lt;p&gt;I also tried to perform the insert &amp;amp; delete on each mongos separately. This did not appear to change the situation.&lt;/p&gt;

&lt;p&gt;I then tried to perform 5 inserts &amp;amp; deletes on each mongos prior to running the tests. This seems to bring the failure rate close to 0% locally but doesn&apos;t affect Evergreen&apos;s failure rate significantly.&lt;/p&gt;

&lt;p&gt;Note also that 14442 is a mongod node behind one of the mongoses that the driver communicates with (this is a sharded cluster of replica sets).&lt;/p&gt;

&lt;p&gt;Example output with the failure: &lt;a href=&quot;https://gist.github.com/p-mongo/a2f09d862ef82e6e538ee8fe4d1db5e5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gist.github.com/p-mongo/a2f09d862ef82e6e538ee8fe4d1db5e5&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Locally the entire test file succeeds about half the time, but it looks like in Evergreen the failure rate is close to 100%.&lt;/p&gt;</comment>
                            <comment id="2313716" author="milkie" created="Fri, 5 Jul 2019 17:49:50 +0000"  >&lt;p&gt;That link points to a line that says &quot;Encountered error from localhost:27217 during a transaction :: caused by :: Read timestamp Timestamp(1562321126, 31) is older than the oldest available timestamp..&quot;.  That message is not the error that this ticket is concerned with.  &lt;/p&gt;

&lt;p&gt;In order for the problem to be the same as this ticket, the error text would need to say &quot;Encountered error from localhost:27019 during a transaction :: caused by :: Unable to read from a snapshot due to pending collection catalog changes; please retry the operation.&quot;.&lt;/p&gt;</comment>
                            <comment id="2313680" author="dmitry.lukyanov" created="Fri, 5 Jul 2019 17:21:32 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=milkie&quot; class=&quot;user-hover&quot; rel=&quot;milkie&quot;&gt;milkie&lt;/a&gt;, I&apos;ve also faced exactly the same error: &lt;a href=&quot;https://evergreen.mongodb.com/task_log_raw/dot_net_driver_unsecure_tests__version~latest_os~windows_64_topology~sharded_cluster_auth~noauth_ssl~nossl_test_patch_385bb3b0be82ba8c053580acf86d327738a13a37_5d1e3063d6d80a40ea74adcf_19_07_04_16_59_16/4?type=T#L2388&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/task_log_raw/dot_net_driver_unsecure_tests__version~latest_os~windows_64_topology~sharded_cluster_auth~noauth_ssl~nossl_test_patch_385bb3b0be82ba8c053580acf86d327738a13a37_5d1e3063d6d80a40ea74adcf_19_07_04_16_59_16/4?type=T#L2388&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We think that these are the same issues which are just thrown from a slightly different place in the test.&lt;/p&gt;</comment>
                            <comment id="2313673" author="milkie" created="Fri, 5 Jul 2019 17:10:43 +0000"  >&lt;p&gt;Reclosing this ticket.  Dimtry, the error message I see appearing in your patch build does not match the message for this ticket.&lt;/p&gt;

&lt;p&gt;It appears that &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-40685&quot; title=&quot;Mongos often fails transactions that use &amp;quot;snapshot&amp;quot; with SnapshotTooOld&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-40685&quot;&gt;&lt;del&gt;SERVER-40685&lt;/del&gt;&lt;/a&gt; is a better match for your message; there are more details about this in that ticket.&lt;/p&gt;</comment>
                            <comment id="2312858" author="dmitry.lukyanov" created="Thu, 4 Jul 2019 14:32:22 +0000"  >&lt;p&gt;Hello &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=milkie&quot; class=&quot;user-hover&quot; rel=&quot;milkie&quot;&gt;milkie&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;probaby I have the same situation: &lt;a href=&quot;https://evergreen.mongodb.com/task_log_raw/dot_net_driver_secure_tests__version~latest_os~windows_64_topology~sharded_cluster_auth~auth_ssl~ssl_test_patch_385bb3b0be82ba8c053580acf86d327738a13a37_5d1d06492fbabe1ad8054e0c_19_07_03_19_47_21/1?type=T#L2304&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/task_log_raw/dot_net_driver_secure_tests__version~latest_os~windows_64_topology~sharded_cluster_auth~auth_ssl~ssl_test_patch_385bb3b0be82ba8c053580acf86d327738a13a37_5d1d06492fbabe1ad8054e0c_19_07_03_19_47_21/1?type=T#L2304&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Even though &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rstam&quot; class=&quot;user-hover&quot; rel=&quot;rstam&quot;&gt;rstam&lt;/a&gt;&apos;s workaround has been applied. I&apos;m continuing an investigation of it. Probably I will reopen this ticket.&lt;/p&gt;</comment>
                            <comment id="2311578" author="milkie" created="Wed, 3 Jul 2019 18:48:45 +0000"  >&lt;p&gt;Ok &amp;#8211; please reopen this if it starts becoming a problem again.&lt;/p&gt;</comment>
                            <comment id="2311573" author="rstam" created="Wed, 3 Jul 2019 18:44:42 +0000"  >&lt;p&gt;It hasn&apos;t failed for me recently.&lt;/p&gt;

&lt;p&gt;This was happening to me on a branch I was working on, and I think since I rebased on master it stopped happening, but I&apos;m not sure what exactly from all the changes I picked up from master might have changed things.&lt;/p&gt;</comment>
                            <comment id="2304941" author="milkie" created="Fri, 28 Jun 2019 16:59:34 +0000"  >&lt;p&gt;Is the test suite still failing?  There are various things we can try to avoid having this particular snapshot error occur for driver tests.&lt;/p&gt;</comment>
                            <comment id="2274579" author="rstam" created="Thu, 6 Jun 2019 19:08:33 +0000"  >&lt;p&gt;Currently the C# driver test suite does not pass due to this server issue.&lt;/p&gt;

&lt;p&gt;Is there any workaround suggested?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="793281">CSHARP-2629</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="701590">SERVER-39704</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="890356">CDRIVER-3301</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="1988194">SERVER-63887</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="938605">RUBY-1942</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>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 28 Jun 2019 16:59:34 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        2 years, 45 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_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>neil.shweky@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            2 years, 45 weeks, 4 days ago
                        </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>dianna.hohensee@mongodb.com</customfieldvalue>
            <customfieldvalue>dmitry.lukyanov@mongodb.com</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>oleg.pudeyev@mongodb.com</customfieldvalue>
            <customfieldvalue>randolph@mongodb.com</customfieldvalue>
            <customfieldvalue>robert@mongodb.com</customfieldvalue>
            <customfieldvalue>reage521@gmail.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hv34qf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hwa5qn:</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_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="3518">Execution Team 2020-01-27</customfieldvalue>
    <customfieldvalue id="3519">Execution Team 2020-02-10</customfieldvalue>
    <customfieldvalue id="3631">Execution Team 2020-03-09</customfieldvalue>
    <customfieldvalue id="3837">Sharding 2020-04-20</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10750" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Steps To Reproduce</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p&gt;I think the repro is:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;create an empty collection&lt;/li&gt;
	&lt;li&gt;followed immediately by an insert in a transaction&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Note: part of the scenario might be creating the collection on one mongos and executing the transaction on a different mongos, but I&apos;m not sure.&lt;/p&gt;</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|hv2qzr:</customfieldvalue>

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