<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:47:21 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-37897] Disable table logging for data files when enableMajorityReadConcern=false</title>
                <link>https://jira.mongodb.org/browse/SERVER-37897</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;In&#160;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-37227&quot; title=&quot;Reintroduce enableMajorityReadConcern:false server parameter&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-37227&quot;&gt;&lt;del&gt;SERVER-37227&lt;/del&gt;&lt;/a&gt;, we reintroduced the &lt;tt&gt;enableMajorityReadConcern:false&lt;/tt&gt; parameter on the master branch. When majority read concern is disabled, we turn on logging for data files and take unstable checkpoints. This is incompatible with causally consistent sharded cluster backup, which requires us to be able to replay the oplog to a particular point in time. We must do the following to disable table logging for data files when &lt;tt&gt;enableMajorityReadConcern=false&lt;/tt&gt;:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Disable table logging for data files, which was enabled &lt;a href=&quot;https://github.com/mongodb/mongo/blob/fb0d42af2b81a64f24c0dc274e26cc0956844d08/src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp#L536-L538&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
	&lt;li&gt;Take stable checkpoints. In addition to &lt;a href=&quot;https://github.com/mongodb/mongo/blob/fb0d42af2b81a64f24c0dc274e26cc0956844d08/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp#L248&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;setting the oldest timestamp&lt;/a&gt; in the &lt;tt&gt;WiredTigerOplogManager&lt;/tt&gt;, we will set the stable timestamp. In the &lt;tt&gt;WiredTigerCheckpointThread&lt;/tt&gt;, we will take a stable checkpoint instead of &lt;a href=&quot;https://github.com/mongodb/mongo/blob/fb0d42af2b81a64f24c0dc274e26cc0956844d08/src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp#L289&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;taking a full checkpoint&lt;/a&gt;. Since we are no longer taking full checkpoints, we may need to &lt;a href=&quot;https://github.com/mongodb/mongo/blob/fb0d42af2b81a64f24c0dc274e26cc0956844d08/src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp#L1679-L1682&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;pin oplog&lt;/a&gt;. Since the stable timestamp is now ahead of the majority commit point, we still must use rollback-via-refetch instead of recover-to-stable-timestamp.&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="628232">SERVER-37897</key>
            <summary>Disable table logging for data files when enableMajorityReadConcern=false</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="tess.avitabile@mongodb.com">Tess Avitabile</assignee>
                                    <reporter username="tess.avitabile@mongodb.com">Tess Avitabile</reporter>
                        <labels>
                    </labels>
                <created>Fri, 2 Nov 2018 15:22:38 +0000</created>
                <updated>Sun, 29 Oct 2023 22:26:55 +0000</updated>
                            <resolved>Mon, 10 Dec 2018 22:29:11 +0000</resolved>
                                                    <fixVersion>4.1.7</fixVersion>
                                    <component>Replication</component>
                    <component>Storage</component>
                                        <votes>0</votes>
                                    <watches>9</watches>
                                                                                                                <comments>
                            <comment id="2086399" author="xgen-internal-githook" created="Mon, 10 Dec 2018 22:28:44 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Tess Avitabile&apos;, &apos;email&apos;: &apos;tess.avitabile@mongodb.com&apos;, &apos;username&apos;: &apos;tessavitabile&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-37897&quot; title=&quot;Disable table logging for data files when enableMajorityReadConcern=false&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-37897&quot;&gt;&lt;del&gt;SERVER-37897&lt;/del&gt;&lt;/a&gt; Disable table logging for data files when enableMajorityReadConcern=false&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/6f23d1a20a7669396efab06bf26b3ee76553fd9b&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/6f23d1a20a7669396efab06bf26b3ee76553fd9b&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2059109" author="milkie" created="Mon, 12 Nov 2018 18:41:39 +0000"  >&lt;p&gt;Regarding my confusion over&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;I imagined that we would call &lt;tt&gt;setStableTimestamp()&lt;/tt&gt; from the oplog manager (which also sets the oldest timestamp). Does that make sense?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;I have edited the Description to suggest that we set both the stable and oldest timestamp in the oplog manager.&lt;/p&gt;</comment>
                            <comment id="2057700" author="william.schultz" created="Fri, 9 Nov 2018 21:23:56 +0000"  >&lt;p&gt;To clarify the discussion with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=daniel.gottlieb&quot; class=&quot;user-hover&quot; rel=&quot;daniel.gottlieb&quot;&gt;daniel.gottlieb&lt;/a&gt; about keeping a &quot;window&quot; of history, I was only concerned with keeping a small bit of &quot;snapshot window&quot; history, so as to service sharded atClusterTime reads more easily. When majority reads are enabled, the storage timeline (i.e. the oplog) looks something like the following, with&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;   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;O=oldest timestamp&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&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;   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;S=stable timestamp&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&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;   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;M=majority committed timestamp&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&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;   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;A=all committed timestamp&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&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;   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;L=last applied timestamp&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&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-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;O-------S----M---------------------------------------A----L&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;The interval between &lt;tt&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;O,S&amp;#93;&lt;/span&gt;&lt;/tt&gt; is not strictly necessary to maintain, but we let the oldest_timestamp lag a bit behind the stable_timestamp so that we could service reads in this region of history if necessary. The amount of lag was calculated and determined by &lt;a href=&quot;https://github.com/mongodb/mongo/blob/a66a5578d5b006cef85b16eac05c96b58c877ebe/src/mongo/db/snapshot_window_options.h#L43&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;these parameters&lt;/a&gt;. When majority reads are disabled, we no longer keep history all the way back to the majority commit point i.e. we will no longer be restricting the stable timestamp to fall &lt;em&gt;behind&lt;/em&gt; the majority commit point. The timeline may now look something like this:&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;-------------M--------------------------O--------S---A----L&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;Depending on the implementation, the stable timestamp (S) may end up always being set to the all committed timestamp (A). Although these diagrams cannot be considered &quot;to scale&quot;, they try to illustrate the issue of setting the stable timestamp &lt;em&gt;behind&lt;/em&gt; the majority commit point: there is a lot of history that needs to be kept between the oldest timestamp and the most recent last applied timestamp (the &lt;span class=&quot;error&quot;&gt;&amp;#91;O,L&amp;#93;&lt;/span&gt; interval in the first diagram). If we start setting the stable timestamp to something much closer to lastApplied/all committed, there is no need to keep all of this history. We still, however, want to keep a &quot;snapshot window&quot;, which is the (much smaller) amount of history we keep around between the oldest timestamp and the stable timestamp. This will allow us to service snapshot reads that may lag a bit behind the lastApplied timestamp. The &quot;snapshot window&quot; history is what we are interested in maintaining as a part of this ticket, which we may just get for free, since we &lt;a href=&quot;https://github.com/mongodb/mongo/blob/aff889b39301472bd2143967938a3dba468dfc63/src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp#L1437-L1438&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;already calculate a window of lag&lt;/a&gt; when we set the stable timestamp in WiredTiger.&lt;/p&gt;</comment>
                            <comment id="2056499" author="william.schultz" created="Thu, 8 Nov 2018 20:28:18 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=daniel.gottlieb&quot; class=&quot;user-hover&quot; rel=&quot;daniel.gottlieb&quot;&gt;daniel.gottlieb&lt;/a&gt; I wasn&apos;t referring to the history we keep all the way back to the majority commit point. I was just referring to the small window of history we keep behind the stable timestamp, as dictated by &lt;a href=&quot;https://github.com/mongodb/mongo/blob/a66a5578d5b006cef85b16eac05c96b58c877ebe/src/mongo/db/snapshot_window_options.h#L45-L64&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;these parameters&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="2053309" author="daniel.gottlieb@10gen.com" created="Tue, 6 Nov 2018 16:48:25 +0000"  >&lt;blockquote&gt;
&lt;p&gt;Ideally, as a part of this change, we would maintain a window of history behind the stable timestamp, as we do already when majority reads are enabled.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;To my knowledge, the problems surrounding memory usage and history, particularly when there&apos;s a problem moving the commit point, are dictating that the purpose of this project/ticket are to not keep history to the majority point. I don&apos;t believe replication/sharding will be able to expect any meaningful history in storage with &lt;tt&gt;enableMajorityReadConcern: false&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="2053177" author="william.schultz" created="Tue, 6 Nov 2018 15:46:50 +0000"  >&lt;p&gt;Ideally, as a part of this change, we would maintain a window of history behind the stable timestamp, as we do already when majority reads are enabled. This is necessary to make single shard transactions against &lt;em&gt;enableMajorityReadConcern:false&lt;/em&gt; nodes work in a sensible way. Depending on how we implement the changes for this ticket, we may get this for free, as a result of the &lt;a href=&quot;https://github.com/mongodb/mongo/blob/c7553b861796c1581c85b3cbc4e55dcc9666aa0f/src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp#L1441-L1442&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;existing logic&lt;/a&gt; in &lt;tt&gt;WiredTigerKVEngine::setStableTimestamp&lt;/tt&gt;. If this is not possible as part of this ticket, we should make sure to do it separately.&lt;/p&gt;</comment>
                            <comment id="2051544" author="tess.avitabile" created="Mon, 5 Nov 2018 14:08:34 +0000"  >&lt;p&gt;I imagined that we would call &lt;tt&gt;setStableTimestamp()&lt;/tt&gt; from the oplog manager (which also sets the oldest timestamp). Does that make sense?&lt;/p&gt;</comment>
                            <comment id="2051238" author="milkie" created="Sun, 4 Nov 2018 20:46:10 +0000"  >&lt;p&gt;This plan sounds a lot better than any of my crazy ideas for this problem.&lt;br/&gt;
Q: If we stop setting the oldest timestamp in the oplog manager, where will we set it instead?  I suppose we could have the checkpoint thread set it, since it will now become the thing that is consuming the oldest history?&lt;/p&gt;</comment>
                            <comment id="2050291" author="tess.avitabile" created="Fri, 2 Nov 2018 15:24:23 +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;, this is the solution that &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=daniel.gottlieb&quot; class=&quot;user-hover&quot; rel=&quot;daniel.gottlieb&quot;&gt;daniel.gottlieb&lt;/a&gt; and I agreed on for causally consistent sharded cluster backups. I&apos;m not sure whether this work belongs on the Replication team or the Storage team. I think it could reasonably be done by either team.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                                        </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="631519">SERVER-38041</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="669232">SERVER-38925</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="623460">SERVER-37728</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_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_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Sun, 4 Nov 2018 20:46:10 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        5 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[<s><a href='https://jira.mongodb.org/browse/INIT-9'>INIT-9</a></s>]]></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_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-1191</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>
                            5 years, 9 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>66.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>daniel.gottlieb@mongodb.com</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>tess.avitabile@mongodb.com</customfieldvalue>
            <customfieldvalue>william.schultz@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hubxe7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|htzevj:</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="2606">Repl 2018-12-03</customfieldvalue>
    <customfieldvalue id="2607">Repl 2018-12-17</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|hubjnj:</customfieldvalue>

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