<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 05:06:03 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-44462] Run listIndexes with a single snapshot during initial sync</title>
                <link>https://jira.mongodb.org/browse/SERVER-44462</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Without this we can get idempotency problems during initial sync. We can try to create two indexes during collection cloning that never existed simultaneously in real life. Eventually we will get a dropIndex oplog entry for one of the two, but at collection clone time we don&apos;t know which one so we can&apos;t just drop one to fix the idempotency violation.&lt;/p&gt;

&lt;p&gt;This was hypothesized while I talked with &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; regarding &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-27122&quot; title=&quot;Restart initial sync for known index idempotency errors; fail for unknown ones. &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-27122&quot;&gt;SERVER-27122&lt;/a&gt;.&lt;/p&gt;</description>
                <environment></environment>
        <key id="991804">SERVER-44462</key>
            <summary>Run listIndexes with a single snapshot during initial sync</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="12300">Won&apos;t Do</resolution>
                                        <assignee username="milkie@mongodb.com">Eric Milkie</assignee>
                                    <reporter username="judah.schvimer@mongodb.com">Judah Schvimer</reporter>
                        <labels>
                    </labels>
                <created>Wed, 6 Nov 2019 19:02:03 +0000</created>
                <updated>Mon, 9 Dec 2019 22:04:57 +0000</updated>
                            <resolved>Mon, 9 Dec 2019 19:59:50 +0000</resolved>
                                                                    <component>Catalog</component>
                    <component>Index Maintenance</component>
                    <component>Replication</component>
                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="2594943" author="judah.schvimer" created="Mon, 9 Dec 2019 22:04:57 +0000"  >&lt;p&gt;I think that this ticket describes idempotency problems that could happen at index creation time in collection cloning. We usually have thought about idempotency problems as happening at oplog application time. I&apos;m fine closing this until we see this happen in reality. It&apos;s possible that fixing the index idempotency problems in oplog application will fix idempotency problems during collection cloning, though I don&apos;t think that will happen automatically.&lt;/p&gt;</comment>
                            <comment id="2594651" author="milkie" created="Mon, 9 Dec 2019 19:59:50 +0000"  >&lt;p&gt;I think Siyuan is correct; this won&apos;t help things.  We need to do the work in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-27122&quot; title=&quot;Restart initial sync for known index idempotency errors; fail for unknown ones. &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-27122&quot;&gt;SERVER-27122&lt;/a&gt; to make headway on this.&lt;/p&gt;</comment>
                            <comment id="2529502" author="judah.schvimer" created="Mon, 11 Nov 2019 20:21:38 +0000"  >&lt;blockquote&gt;
&lt;p&gt;Eric Milkie, can we relax those constraints in initial sync?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;From discussing with &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;, our plan is for execution to do &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-27122&quot; title=&quot;Restart initial sync for known index idempotency errors; fail for unknown ones. &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-27122&quot;&gt;SERVER-27122&lt;/a&gt; to allow &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33946&quot; title=&quot;Decrease number of initial sync attempts in tests to 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33946&quot;&gt;SERVER-33946&lt;/a&gt; to reduce the number of initial sync attempts to 1, and then solve the idempotency problems based on amount of user pain. Some like the number of indexes and number of text indexes may be easy to relax, others like having different specs but the same name may be difficult to relax.&lt;/p&gt;</comment>
                            <comment id="2529490" author="judah.schvimer" created="Mon, 11 Nov 2019 20:17:56 +0000"  >&lt;p&gt;I agree reading from a snapshot won&apos;t solve all index idempotency problems. The concern was that solutions to the already known tickets linked to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33946&quot; title=&quot;Decrease number of initial sync attempts in tests to 1&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33946&quot;&gt;SERVER-33946&lt;/a&gt; would not necessarily be sufficient to solve this class of problems.&lt;/p&gt;</comment>
                            <comment id="2529384" author="siyuan.zhou@10gen.com" created="Mon, 11 Nov 2019 19:56:08 +0000"  >&lt;p&gt;Reading indexes from a single snapshot isn&apos;t sufficient. In the cases &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=robert.guo&quot; class=&quot;user-hover&quot; rel=&quot;robert.guo&quot;&gt;robert.guo&lt;/a&gt; listed in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-27122&quot; title=&quot;Restart initial sync for known index idempotency errors; fail for unknown ones. &quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-27122&quot;&gt;SERVER-27122&lt;/a&gt;, the indexes are all read from a single snapshot. We probably need to fix them case by case.&lt;/p&gt;

&lt;p&gt;1. creating indexes with different specs but the same name.&lt;br/&gt;
This will be fixed in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-32225&quot; title=&quot;Initial sync should ignore multiple text indexes on same collection error&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-32225&quot;&gt;&lt;del&gt;SERVER-32225&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;2. creating text indexes with different specs.&lt;br/&gt;
3. having more than 64 indexes combined, before and after dropping a collection.&lt;br/&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;, can we relax those constraints in initial sync?&lt;/p&gt;

&lt;p&gt;Alternatively, we can also develop a solution based on indexes read from a snapshot. We need to make sure the entries that changed indexes before this snapshot&apos;s timestamp are ignored.&lt;/p&gt;</comment>
                            <comment id="2528548" author="judah.schvimer" created="Mon, 11 Nov 2019 15:45:53 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=tess.avitabile&quot; class=&quot;user-hover&quot; rel=&quot;tess.avitabile&quot;&gt;tess.avitabile&lt;/a&gt; asked what happens today, create both indexes or choose one. I &lt;em&gt;think&lt;/em&gt; we would attempt to create both and get various errors depending on how the indexes are mismatched. We haven&apos;t tested this though, and so the first step should be testing with various indexes known to be incompatible to see the behavior.&lt;/p&gt;</comment>
                            <comment id="2528493" author="milkie" created="Mon, 11 Nov 2019 15:37:17 +0000"  >&lt;p&gt;I was mistaken; this should go on Execution for scheduling.&lt;/p&gt;</comment>
                            <comment id="2528465" author="judah.schvimer" created="Mon, 11 Nov 2019 15:33:06 +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; thought this was a query request since the change lives in the &lt;tt&gt;listIndexes&lt;/tt&gt; command. If you think that&apos;s incorrect, I can put it on repl.&lt;/p&gt;</comment>
                            <comment id="2526458" author="charlie.swanson" created="Sat, 9 Nov 2019 01:56:58 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=judah.schvimer&quot; class=&quot;user-hover&quot; rel=&quot;judah.schvimer&quot;&gt;judah.schvimer&lt;/a&gt; is this supposed to be on the query team&apos;s backlog? I&apos;m not sure I&apos;d know exactly where to start for such a task or how to test it. It does seem in-between query and repl, but I thought I&apos;d check if this was a mistake before we triage.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="491093">SERVER-33946</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="333012">SERVER-27122</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>9.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sat, 9 Nov 2019 01:56:58 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        4 years, 9 weeks, 2 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>judah.schvimer@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            4 years, 9 weeks, 2 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>charlie.swanson@mongodb.com</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>judah.schvimer@mongodb.com</customfieldvalue>
            <customfieldvalue>siyuan.zhou@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hw0wpj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hvp7rr:</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="3400">Execution Team 2019-12-02</customfieldvalue>
    <customfieldvalue id="3401">Execution Team 2019-12-16</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|hw0iyv:</customfieldvalue>

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