<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:37:19 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-34632] config.chunks change to config.cache.chunks creates a collection long name after upgrade</title>
                <link>https://jira.mongodb.org/browse/SERVER-34632</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;After upgrading from 3.4 to 3.6 I get many of these errors for different sharded collections:&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: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;I SHARDING [ShardServerCatalogCacheLoader-4] InvalidNamespace: Failed to update the persisted chunk metadata for collection &apos;easypalletideas-uorzoqjxdxhndfy_stackpat_40594.easypalletideas-uorzoqjxdxhndfy_stackpat_40594_counters_hourly&apos; from &apos;0|0||000000000000000000000000&apos; to &apos;1|0||5adc9e47ed72f1e7708a691d&apos; due to &apos;fully qualified namespace config.cache.chunks.easypalletideas-uorzoqjxdxhndfy_stackpat_40594.easypalletideas-uorzoqjxdxhndfy_stackpat_40594_counters_hourly is too long (max is 120 bytes)&apos;. Will be retried.&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;This did not happen before the upgrade.&lt;/p&gt;

&lt;p&gt;I suspect the issue is the change in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-31644&quot; title=&quot;Rename the per-shard filtering information cache collections to be prefixed with `config.cache`&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-31644&quot;&gt;&lt;del&gt;SERVER-31644&lt;/del&gt;&lt;/a&gt; is making the collection name too long despite the original collection being within limits.&lt;/p&gt;</description>
                <environment></environment>
        <key id="533106">SERVER-34632</key>
            <summary>config.chunks change to config.cache.chunks creates a collection long name after upgrade</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="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="backlog-server-catalog-and-routing">Backlog - Catalog and Routing</assignee>
                                    <reporter username="Rybak">Shay</reporter>
                        <labels>
                            <label>SSCCL-BUG</label>
                            <label>oldshardingemea</label>
                    </labels>
                <created>Tue, 24 Apr 2018 11:08:16 +0000</created>
                <updated>Thu, 26 Oct 2023 09:51:47 +0000</updated>
                                            <version>3.6.4</version>
                                                    <component>Sharding</component>
                                        <votes>4</votes>
                                    <watches>32</watches>
                                                                                                                <comments>
                            <comment id="4129719" author="kaloian.manassiev" created="Mon, 18 Oct 2021 15:38:31 +0000"  >&lt;p&gt;The feature was disabled in 5.1 (under &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-58367&quot; title=&quot;Create Feature flag for PM-2384&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-58367&quot;&gt;&lt;del&gt;SERVER-58367&lt;/del&gt;&lt;/a&gt;) until we reach agreement on the backwards-compatibility implications during downgrade.&lt;/p&gt;</comment>
                            <comment id="3924747" author="xgen-internal-githook" created="Fri, 9 Jul 2021 07:36:53 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Antonio Fuschetto&apos;, &apos;email&apos;: &apos;antonio.fuschetto@mongodb.com&apos;, &apos;username&apos;: &apos;afuschetto&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34632&quot; title=&quot;config.chunks change to config.cache.chunks creates a collection long name after upgrade&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34632&quot;&gt;SERVER-34632&lt;/a&gt; config.chunks change to config.cache.chunks creates a collection long name after upgrade&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/33aaa656979089a8d6530d1ae3ff15335b13508a&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/33aaa656979089a8d6530d1ae3ff15335b13508a&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3917305" author="JIRAUSER1259062" created="Tue, 6 Jul 2021 07:41:07 +0000"  >&lt;p&gt;Code review url:&#160;&lt;a href=&quot;https://mongodbcr.appspot.com/798010001&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodbcr.appspot.com/798010001&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2092797" author="jviera@fuze.com" created="Mon, 17 Dec 2018 16:05:47 +0000"  >&lt;p&gt;Is there any update, ETA or workaround available for this other than renaming the collections? Thanks!&lt;/p&gt;</comment>
                            <comment id="1901103" author="xgen-internal-githook" created="Thu, 24 May 2018 17:23:14 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;kaloianm&apos;, &apos;name&apos;: &apos;Kaloian Manassiev&apos;, &apos;email&apos;: &apos;kaloian.manassiev@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34632&quot; title=&quot;config.chunks change to config.cache.chunks creates a collection long name after upgrade&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34632&quot;&gt;SERVER-34632&lt;/a&gt; Rename `struct dbTask` to DBTask&lt;/p&gt;

&lt;p&gt;... to follow naming conventions&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/b919fb48eb611b3c8cbba9d7f03f6df1d25d4cd5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/b919fb48eb611b3c8cbba9d7f03f6df1d25d4cd5&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1901102" author="xgen-internal-githook" created="Thu, 24 May 2018 17:23:12 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;kaloianm&apos;, &apos;name&apos;: &apos;Kaloian Manassiev&apos;, &apos;email&apos;: &apos;kaloian.manassiev@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34632&quot; title=&quot;config.chunks change to config.cache.chunks creates a collection long name after upgrade&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34632&quot;&gt;SERVER-34632&lt;/a&gt; Use alias for the callback of CatalogCacheLoader::getChunksSince&lt;/p&gt;

&lt;p&gt;Also use StringMap in CollectionShardingState instead of std::unordered_map.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/cb0393248d26e21e69efde15d9d3965293ead29b&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/cb0393248d26e21e69efde15d9d3965293ead29b&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1892700" author="esha.maharishi@10gen.com" created="Wed, 16 May 2018 13:38:20 +0000"  >&lt;p&gt;I agree, since the 3.6.5 primary&apos;s behavior in the mixed-version replica set is pretty much the same as before the fix.&lt;/p&gt;

&lt;p&gt;It might be good to confirm that the 3.6.6 secondary will fail reads with non-available readConcern in this case.&lt;/p&gt;</comment>
                            <comment id="1892691" author="kaloian.manassiev" created="Wed, 16 May 2018 13:33:26 +0000"  >&lt;p&gt;Remember that this will be backported to 3.6 as well. But yes, if a 3.6.6 node is promoted to a primary, manages to create the view and then a 3.6.5 is promoted to a primary before the entire shard is upgraded, the 3.6.5 primary will fail. Getting out of this situation will either require finishing the upgrade or downgrading to 3.6.5 and manually deleting the created views.&lt;/p&gt;

&lt;p&gt;I think that this is a reasonable tradeoff to what would otherwise require writing to two collections (UUID and namespace) and a complex handoff protocol about which collection the secondaries should be reading from.&lt;/p&gt;</comment>
                            <comment id="1892679" author="esha.maharishi@10gen.com" created="Wed, 16 May 2018 13:25:49 +0000"  >&lt;p&gt;Hmm, ok, and finally, how does this work in a mixed-version replica set (say two nodes, one is 3.6.x, other is 4.0)?&lt;/p&gt;

&lt;p&gt;If the 3.6.x node steps up, will it try to write to &quot;config.cache.chunks.&amp;lt;ns&amp;gt;&quot;, see it&apos;s a view, and fail?&lt;/p&gt;</comment>
                            <comment id="1891669" author="kaloian.manassiev" created="Tue, 15 May 2018 14:54:50 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=esha.maharishi&quot; class=&quot;user-hover&quot; rel=&quot;esha.maharishi&quot;&gt;esha.maharishi&lt;/a&gt;, I edited the description above to clarify. The drop of the namespace-suffixed collections will happen as part of the regular update of the cache collection. The sequence is: set the cache collection as &quot;in-update&quot; (which will cause the secondaries to disregard what they read and wait until the &quot;in-update&quot; flag is cleared), drop the namespace-suffxied collection (this means secondaries can get no chunks, but it doesn&apos;t matter because the will loop around and retry), then create the UUID-suffixed collection + the view (only if the view name doesn&apos;t exceed the name size limitations, which I think there shouldn&apos;t be any).&lt;/p&gt;</comment>
                            <comment id="1891627" author="esha.maharishi@10gen.com" created="Tue, 15 May 2018 14:30:36 +0000"  >&lt;p&gt;The view idea sounds neat. Couple questions -&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;The primary node will first drop the namespace-suffixed collection, then construct a UUID-named one&#160;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;When will this occur? (On startup/transition to primary; on setFCV=4.0?).&lt;/p&gt;

&lt;p&gt;Will the drop + creates be atomic? (We might be able to just drop, and let the next refresh do the creates?)&lt;/p&gt;

&lt;p&gt;Using config.cache.chunks.&amp;lt;uuid&amp;gt; might also solve&#160;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34878&quot; title=&quot;if setShardVersion for dropCollection not sent and collection re-created, migrations for new collection can fail indefinitely&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34878&quot;&gt;&lt;del&gt;SERVER-34878&lt;/del&gt;&lt;/a&gt; and&#160;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-34904&quot; title=&quot;recipient shard may be unable to accept versioned requests if it doesn&amp;#39;t receive setShardVersion for drop and collection is recreated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-34904&quot;&gt;&lt;del&gt;SERVER-34904&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="1891546" author="kaloian.manassiev" created="Tue, 15 May 2018 13:47:26 +0000"  >&lt;p&gt;The plan is to fix this problem though the following changes:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Uncomplicate the ShardServerCatalogCacheLoader a bit, because currently the logic within it is really &lt;a href=&quot;https://github.com/mongodb/mongo/blob/0192520fa62db28787a5fb6ad828c1723d7d992c/src/mongo/db/s/shard_server_catalog_cache_loader.cpp#L805&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;tangled together&lt;/a&gt; and not very malleable to changes. I plan on pulling out the management of the &lt;tt&gt;config.system.cache.chunks/collections&lt;/tt&gt; plus the in-memory queues to a separate class called &lt;tt&gt;RoutingInfoCacheCollection&lt;/tt&gt; which can be unit-tested. This class will be the means to interact with the cache collections. Along with this I plan to throw out most of the StatusWith usages and replacing them with exceptions.&lt;/li&gt;
	&lt;li&gt;The primary node, as part of the &quot;in-update&quot; logic which it currently uses, will first drop the namespace-suffixed collection, then construct a UUID-named one and, in order to preserve backwards compatibility with 3.6.x versions which do not contain this fix, will also &lt;a href=&quot;https://docs.mongodb.com/manual/reference/command/create/#dbcmd.create&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;create a view&lt;/a&gt; with the namespace-named collection which is an alias for the UUID.&lt;/li&gt;
	&lt;li&gt;The secondary nodes will first look for an UUID-suffixed cache collection and read from it and if that is not available, then back-off to the name-suffixed cache collection only (not that there is no need to look for the view, because the presence of a view means that there must be a UUID-suffixed cache collection).&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=renctan&quot; class=&quot;user-hover&quot; rel=&quot;renctan&quot;&gt;renctan&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=esha.maharishi&quot; class=&quot;user-hover&quot; rel=&quot;esha.maharishi&quot;&gt;esha.maharishi&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=schwerin&quot; class=&quot;user-hover&quot; rel=&quot;schwerin&quot;&gt;schwerin&lt;/a&gt;, can you please review this plan?&lt;/p&gt;</comment>
                            <comment id="1878208" author="rybak" created="Mon, 30 Apr 2018 18:32:15 +0000"  >&lt;p&gt;Hi Kal,&lt;/p&gt;

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

&lt;p&gt;Thank you for your response.&lt;/p&gt;

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

&lt;p&gt;We are working on shortening the collection names, however, this is hard to do without downtime to our application.&lt;/p&gt;

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

&lt;p&gt;I would suggest until a fix is made to add a comment to the limits documentation and the upgrade documentation from 3.4 to 3.6 to help others avoid this issue.&lt;/p&gt;

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

&lt;p&gt;please update when you have an estimate of when a fix will be made available, and what changes will be made.&lt;/p&gt;

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

&lt;p&gt;Regards,&lt;/p&gt;

&lt;p&gt;&#160; Shay&lt;/p&gt;</comment>
                            <comment id="1878179" author="kaloian.manassiev" created="Mon, 30 Apr 2018 18:18:52 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=Rybak&quot; class=&quot;user-hover&quot; rel=&quot;Rybak&quot;&gt;Rybak&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Sorry for the silence on this ticket. We are aware of what is causing the problem and are working on coming up with a solution.&#160;Unfortunately there is no workaround currently other than using a shorter collection name (I noticed there is some name duplication in the collection name you pasted).&lt;/p&gt;

&lt;p&gt;To give you a little bit of context: these warning messages are indication that the shard chunk filtering metadata could not be persisted on the primary and as such reads against secondary nodes with anything other than the &lt;a href=&quot;https://docs.mongodb.com/manual/reference/read-concern-available/#read-concern-available&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;default read concern&lt;/a&gt;&#160;will not work. In addition, because these failed operations are retried internally, they may build-up in-memory state overtime and cause the server&apos;s memory usage to grow unbounded.&lt;/p&gt;

&lt;p&gt;Apologies for the inconvenience and please continue monitoring this ticket for when this fix will be available.&lt;/p&gt;

&lt;p&gt;Best regards,&lt;/p&gt;

&lt;p&gt;-Kal.&lt;/p&gt;

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

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="1306191">SERVER-47372</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="919015">SERVER-43217</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                            <outwardlinks description="documents">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="1539051">SERVER-52765</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="546479">SERVER-35092</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>14.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="26387"><![CDATA[Catalog and Routing]]></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[[500A000000bMTAtIAO, 5002K00000gjusMQAQ, 5002K00000iOcPDQA0, 5002K00000oejocQAA, 5002K00000scuFrQAI, 5002K00000tVieTQAS, 5002K00000tSJl7QAG]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 30 Apr 2018 18:18:52 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        2 years, 16 weeks, 2 days 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-47372'>SERVER-47372</a></s>, <a href='https://jira.mongodb.org/browse/PM-2948'>PM-2948</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_17050" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Downstream Team Attention</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16941"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-2948</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>dbeng-pm-bot</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            2 years, 16 weeks, 2 days 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_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>antonio.fuschetto@mongodb.com</customfieldvalue>
            <customfieldvalue>backlog-server-catalog-and-routing</customfieldvalue>
            <customfieldvalue>esha.maharishi@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>jviera@fuze.com</customfieldvalue>
            <customfieldvalue>kaloian.manassiev@mongodb.com</customfieldvalue>
            <customfieldvalue>Rybak</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|htw9lb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hykdq7:</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="2290">Sharding 2018-05-21</customfieldvalue>
    <customfieldvalue id="2291">Sharding 2018-06-04</customfieldvalue>
    <customfieldvalue id="2292">Sharding 2018-06-18</customfieldvalue>
    <customfieldvalue id="2385">Sharding 2018-07-02</customfieldvalue>
    <customfieldvalue id="2386">Sharding 2018-07-16</customfieldvalue>
    <customfieldvalue id="2387">Sharding 2018-07-30</customfieldvalue>
    <customfieldvalue id="2451">Sharding 2018-08-13</customfieldvalue>
    <customfieldvalue id="4978">Sharding EMEA 2021-06-14</customfieldvalue>
    <customfieldvalue id="4979">Sharding EMEA 2021-06-28</customfieldvalue>
    <customfieldvalue id="4980">Sharding EMEA 2021-07-12</customfieldvalue>

                        </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|htvvtj:</customfieldvalue>

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