<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:24: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>[DRIVERS-2049] Reinstate readConcern snapshot test on sharded cluster after 4.2.1 is released</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2049</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;In SPEC-1411 we removed testing of read concern snapshot on sharded clusters. However in HELP-10518, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=dianna.hohensee&quot; class=&quot;user-hover&quot; rel=&quot;dianna.hohensee&quot;&gt;dianna.hohensee&lt;/a&gt; mentions that &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-42205&quot; title=&quot;Raise the snapshot window&amp;#39;s cache pressure threshold from 50 to 95&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-42205&quot;&gt;&lt;del&gt;SERVER-42205&lt;/del&gt;&lt;/a&gt; might help avoid these snapshot errors so once 4.2.1 is released we can try reinstate the snapshot test(s). Basically we should revert part (or all) of the changes in SPEC-1411 and see if the tests pass.&lt;/p&gt;</description>
                <environment></environment>
        <key id="922846">DRIVERS-2049</key>
            <summary>Reinstate readConcern snapshot test on sharded cluster after 4.2.1 is released</summary>
                <type id="14901" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14700&amp;avatarType=issuetype">Spec Change</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="shane.harvey@mongodb.com">Shane Harvey</reporter>
                        <labels>
                    </labels>
                <created>Tue, 10 Sep 2019 21:29:55 +0000</created>
                <updated>Thu, 31 Mar 2022 14:10:30 +0000</updated>
                                                                <component>Transactions</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="2600435" author="dianna.hohensee" created="Thu, 12 Dec 2019 02:17:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=shane.harvey&quot; class=&quot;user-hover&quot; rel=&quot;shane.harvey&quot;&gt;shane.harvey&lt;/a&gt;, no, the server has not been updated since the resolution of &lt;a href=&quot;https://jira.mongodb.org/browse/WT-5124&quot; title=&quot;Investigate why the WT lookaside score can be high when 1% of the cache is in use and no evictions occur&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-5124&quot;&gt;&lt;del&gt;WT-5124&lt;/del&gt;&lt;/a&gt;. I believe further server work still must be done &amp;#8211; though &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-42205&quot; title=&quot;Raise the snapshot window&amp;#39;s cache pressure threshold from 50 to 95&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-42205&quot;&gt;&lt;del&gt;SERVER-42205&lt;/del&gt;&lt;/a&gt; may have mitigated (dubious about eliminated) the problem for the Drivers tests. There is not currently any ticket to follow for that work: we do not currently have consensus about what to do among the interested parties.&lt;/p&gt;</comment>
                            <comment id="2597068" author="shane.harvey" created="Tue, 10 Dec 2019 18:24:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=dianna.hohensee&quot; class=&quot;user-hover&quot; rel=&quot;dianna.hohensee&quot;&gt;dianna.hohensee&lt;/a&gt;, from &lt;a href=&quot;https://jira.mongodb.org/browse/WT-5124&quot; title=&quot;Investigate why the WT lookaside score can be high when 1% of the cache is in use and no evictions occur&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-5124&quot;&gt;&lt;del&gt;WT-5124&lt;/del&gt;&lt;/a&gt; it looks like we realized that the server was using the incorrect metric to estimate cache pressure. Was the server updated to use a different approach? Do you think 4.2.2 will have resolved this issue? &lt;/p&gt;</comment>
                            <comment id="2594214" author="esha.bhargava" created="Mon, 9 Dec 2019 17:24:27 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=shane.harvey&quot; class=&quot;user-hover&quot; rel=&quot;shane.harvey&quot;&gt;shane.harvey&lt;/a&gt;4.2.1 is out. Test this when you get a chance to.&lt;/p&gt;</comment>
                            <comment id="2421297" author="dianna.hohensee" created="Mon, 16 Sep 2019 13:48:58 +0000"  >&lt;p&gt;Yes, &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-42205&quot; title=&quot;Raise the snapshot window&amp;#39;s cache pressure threshold from 50 to 95&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-42205&quot;&gt;&lt;del&gt;SERVER-42205&lt;/del&gt;&lt;/a&gt; could have had an effect. Otherwise, if it doesn&apos;t, you&apos;ll probably be interested in the outcome of &lt;a href=&quot;https://jira.mongodb.org/browse/WT-5124&quot; title=&quot;Investigate why the WT lookaside score can be high when 1% of the cache is in use and no evictions occur&quot; class=&quot;issue-link&quot; data-issue-key=&quot;WT-5124&quot;&gt;&lt;del&gt;WT-5124&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                            <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10951" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Driver Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10748"><![CDATA[Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr4puv:</customfieldvalue>

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