<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:32:52 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-33272] The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.</title>
                <link>https://jira.mongodb.org/browse/SERVER-33272</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;We can demote the lock needed for DatabaseHolder::close() from an exclusive global lock to a database exclusive lock as the DatabaseHolder is protected by a mutex. With this, we can also remove the exclusive global locks needed in the dropDatabase command.&lt;/p&gt;

&lt;p&gt;Old Description:&lt;br/&gt;
Currently, the kv engine does not check to see if a database is empty after a collection drop. Thus, empty databases can persist until mongod restarts (or the catalog is reloaded via replication rollback to stable timestamp). This situation is usually benign, but a database entry&apos;s presence does do one thing: it enforces that no other databases that are spelled the same but differ in capitalization can be created.&lt;br/&gt;
Because recover-to-timestamp exists, it can result in some replica set nodes having a catalog entry for an empty database while other nodes do not have such an entry. This can result in the ability to crash secondary nodes that have an empty database entry that a primary node does not have - by attempting to create a database with a different case than the existing empty database entry.&lt;/p&gt;

&lt;p&gt;To fix this, we can check to see if a database is empty (i.e., no collection entries remain in the catalog) after a collection drop. If it is indeed empty, we can attempt to close the database by locking it in X mode and calling DatabaseHolder::close().&lt;/p&gt;</description>
                <environment></environment>
        <key id="496684">SERVER-33272</key>
            <summary>The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</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="gregory.wlodarek@mongodb.com">Gregory Wlodarek</assignee>
                                    <reporter username="milkie@mongodb.com">Eric Milkie</reporter>
                        <labels>
                    </labels>
                <created>Mon, 12 Feb 2018 18:27:42 +0000</created>
                <updated>Sun, 29 Oct 2023 22:34:49 +0000</updated>
                            <resolved>Wed, 9 Oct 2019 20:33:38 +0000</resolved>
                                                    <fixVersion>4.3.1</fixVersion>
                    <fixVersion>4.2.2</fixVersion>
                                    <component>Storage</component>
                                        <votes>0</votes>
                                    <watches>7</watches>
                                                                                                                <comments>
                            <comment id="2484711" author="xgen-internal-githook" created="Wed, 16 Oct 2019 14:09:32 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Gregory Wlodarek&apos;, &apos;username&apos;: &apos;GWlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&lt;br/&gt;
Branch: v4.2&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/1a42e98facd32e981104074d0087ddec55758425&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/1a42e98facd32e981104074d0087ddec55758425&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2474653" author="gregory.wlodarek" created="Wed, 9 Oct 2019 20:38:27 +0000"  >&lt;p&gt;The work for this ticket has been committed &lt;a href=&quot;https://github.com/mongodb/mongo/commit/d743246d3c0e35c21b4f1d954bc138df60c47a5a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="2474624" author="gregory.wlodarek" created="Wed, 9 Oct 2019 20:31:36 +0000"  >&lt;p&gt;Please see &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-43925&quot; title=&quot;Proactively close newly empty databases&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-43925&quot;&gt;SERVER-43925&lt;/a&gt; for the continuation of the ticket for proactively close newly empty databases.&lt;/p&gt;</comment>
                            <comment id="2472092" author="gregory.wlodarek" created="Tue, 8 Oct 2019 18:03:57 +0000"  >&lt;p&gt;After discussing with the team, we&apos;re going to set this ticket aside as there&apos;s no urgency for it right now and needs more work to be done before tackling it.&lt;br/&gt;
 To be able to do this ticket we&apos;ll need to do the following beforehand in order:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Get rid of readConcernMajority=false.&lt;/li&gt;
&lt;/ul&gt;


&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Get rid of two-phase database drops. The database object today doesn&apos;t contain any special state except for the isDropPending flag. We can remove the dropDatabase oplog entry and rollback handler.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is problematic to do today because if we remove the Database in the DatabaseHolder when the last collection is dropped, then we lose our isDropPending flag (a member of the Database object class). This flag prevents new collections from being created on the database while waiting for the second phase of collection drops to be majority committed when using majority read concern. &lt;br/&gt;
 While waiting for the majority point to be reached, a new collection can be created, which will implicitly open the database with the same name while there are collections still drop pending for that database name. Once the majority point is reached, the newly created collection would be forcefully one phase dropped.&lt;/p&gt;

&lt;p&gt;Timeline of events if we implicitly close empty databases today&lt;/p&gt;

&lt;p&gt;Client 1:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;dropDatabase command executed, isDropPending flag set.&lt;/li&gt;
	&lt;li&gt;First phase drop for Coll A
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;Replicate...&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;First phase drop for Coll B
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;Replicate...&lt;/li&gt;
		&lt;li&gt;Close Database in DatabaseHolder since it&apos;s empty now.&lt;/li&gt;
		&lt;li&gt;Replicate...&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Client 2:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Create collection C on the same database (the isDropPending flag would&apos;ve prevented this).
	&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
		&lt;li&gt;Replicate openDB() and createCollection()...&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Client 1:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Majority point reached, second phase of drops executed and committed across all nodes.&lt;/li&gt;
	&lt;li&gt;Forcefully one phase drops collection C created by &apos;Client 2&apos;.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Another issue that would occur is during rollback. When the last collection is first phase dropped and rollback occurs, the Database object will no longer exist in the DatabaseHolder.&lt;/p&gt;</comment>
                            <comment id="2388398" author="xgen-internal-githook" created="Tue, 27 Aug 2019 13:52:47 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;GWlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;, &apos;name&apos;: &apos;Gregory Wlodarek&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; Proactively close newly empty databases&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit 40f226b5a9bfb4863268334d287a46fb226a22cf.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/077f247b29e9f6c5afecec11bb41858ae95067b6&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/077f247b29e9f6c5afecec11bb41858ae95067b6&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2387514" author="xgen-internal-githook" created="Tue, 27 Aug 2019 00:13:08 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Gregory Wlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;, &apos;username&apos;: &apos;GWlodarek&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; Proactively close newly empty databases&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/40f226b5a9bfb4863268334d287a46fb226a22cf&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/40f226b5a9bfb4863268334d287a46fb226a22cf&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2384148" author="xgen-internal-githook" created="Fri, 23 Aug 2019 13:13:10 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;GWlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;, &apos;name&apos;: &apos;Gregory Wlodarek&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; Proactively close newly empty databases&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit b6b81f34516ba7b1472cb1dd319da8785f24ae58.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/e51927f743d0b5bf13e13873f7cfcc1cf07c967a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/e51927f743d0b5bf13e13873f7cfcc1cf07c967a&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2383656" author="xgen-internal-githook" created="Fri, 23 Aug 2019 02:17:20 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Gregory Wlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;, &apos;username&apos;: &apos;GWlodarek&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; Proactively close newly empty databases&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/b6b81f34516ba7b1472cb1dd319da8785f24ae58&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/b6b81f34516ba7b1472cb1dd319da8785f24ae58&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2383652" author="xgen-internal-githook" created="Fri, 23 Aug 2019 02:12:58 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;GWlodarek&apos;, &apos;email&apos;: &apos;gregory.wlodarek@mongodb.com&apos;, &apos;name&apos;: &apos;Gregory Wlodarek&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-33272&quot; title=&quot;The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-33272&quot;&gt;&lt;del&gt;SERVER-33272&lt;/del&gt;&lt;/a&gt; The DatabaseHolder::close() function no longer requires a global write lock and neither does the dropDatabase command.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/d743246d3c0e35c21b4f1d954bc138df60c47a5a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/d743246d3c0e35c21b4f1d954bc138df60c47a5a&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2103152" author="milkie" created="Wed, 2 Jan 2019 15:35:25 +0000"  >&lt;p&gt;After some discussion with Esha, I have decided to pull this QW ticket from the project, as it will exacerbate an existing problem with unsharded databases.  See &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34431&quot; title=&quot;Move DatabaseShardingState into its own map to correctly handle database versioning in face of drop/recreate&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34431&quot;&gt;&lt;del&gt;SERVER-34431&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
The problem today is that certain sharding refresh logic is currently hooked into the dropDatabase command; it is missed when databases are implicitly dropped by individual drops of all collections.  Once &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34431&quot; title=&quot;Move DatabaseShardingState into its own map to correctly handle database versioning in face of drop/recreate&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34431&quot;&gt;&lt;del&gt;SERVER-34431&lt;/del&gt;&lt;/a&gt; is fixed, we can proceed with the work in this ticket.&lt;/p&gt;</comment>
                            <comment id="2103103" author="esha.maharishi@10gen.com" created="Wed, 2 Jan 2019 15:06:03 +0000"  >&lt;p&gt;This may have implications for sharding, since the list of databases is also stored in the routing table on the config server.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10420">
                    <name>Backports</name>
                                            <outwardlinks description="backported by">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="525968">SERVER-34431</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="964785">SERVER-43890</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="616718">SERVER-37552</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="551292">SERVER-35283</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="832999">SERVER-42053</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                                                <inwardlinks description="is documented by">
                                        <issuelink>
            <issuekey id="904641">DOCS-12980</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10620">
                    <name>Issue split</name>
                                            <outwardlinks description="split to">
                                        <issuelink>
            <issuekey id="966052">SERVER-43925</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="split from">
                                        <issuelink>
            <issuekey id="920953">SERVER-43242</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="832999">SERVER-42053</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>11.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_12450" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Backport Requested</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16775"><![CDATA[v4.2]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 12 Jul 2018 02:39:10 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        4 years, 17 weeks ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<s><a href='https://jira.mongodb.org/browse/SERVER-34431'>SERVER-34431</a></s>, <a href='https://jira.mongodb.org/browse/SERVER-43890'>SERVER-43890</a>]]></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>When the last collection in a database is dropped, then the database gets closed as part of the collection drop.&lt;br/&gt;
&lt;br/&gt;
In addition to the work done above, the `dropDatabase` command no longer requires a global exclusive lock but instead only needs a database exclusive lock to drop a database.</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>luke.bonanomi@mongodb.com</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>esha.maharishi@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>gregory.wlodarek@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|htq6lj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6oaf:</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_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="3091">Execution Team 2019-08-12</customfieldvalue>
    <customfieldvalue id="3092">Execution Team 2019-08-26</customfieldvalue>
    <customfieldvalue id="3210">Execution Team 2019-09-09</customfieldvalue>
    <customfieldvalue id="3211">Execution Team 2019-09-23</customfieldvalue>
    <customfieldvalue id="3212">Execution Team 2019-10-07</customfieldvalue>
    <customfieldvalue id="3213">Execution Team 2019-10-21</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_17051" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Teams Impacted</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16943"><![CDATA[Cloud]]></customfieldvalue>
    <customfieldvalue key="16944"><![CDATA[Docs]]></customfieldvalue>
    <customfieldvalue key="16945"><![CDATA[Drivers]]></customfieldvalue>
    <customfieldvalue key="16946"><![CDATA[Triage and Release]]></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|htpsqn:</customfieldvalue>

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