<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:50:41 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-38994] Step down on SIGTERM</title>
                <link>https://jira.mongodb.org/browse/SERVER-38994</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Kubernetes uses SIGTERM to spin down containers, and our sysv init and systemd unit files use SIGTERM to shutdown the mongodb service. It would greatly reduce election time and prevent potential data loss due to replicaset rollback if we were able to use the election handoff path of stepdown instead of waiting for the full electionTimeoutMillis.&lt;/p&gt;</description>
                <environment></environment>
        <key id="672196">SERVER-38994</key>
            <summary>Step down on SIGTERM</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="13201">Fixed</resolution>
                                        <assignee username="mira.carey@mongodb.com">Mira Carey</assignee>
                                    <reporter username="alyson.cabral@mongodb.com">Alyson Cabral</reporter>
                        <labels>
                    </labels>
                <created>Mon, 14 Jan 2019 20:26:06 +0000</created>
                <updated>Sun, 29 Oct 2023 22:25:08 +0000</updated>
                            <resolved>Fri, 15 Mar 2019 22:57:57 +0000</resolved>
                                                    <fixVersion>3.6.15</fixVersion>
                    <fixVersion>4.0.8</fixVersion>
                    <fixVersion>4.1.10</fixVersion>
                                    <component>Replication</component>
                                        <votes>0</votes>
                                    <watches>22</watches>
                                                                                                                <comments>
                            <comment id="2436747" author="xgen-internal-githook" created="Fri, 27 Sep 2019 16:36:05 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Rahul Sundararaman&apos;, &apos;email&apos;: &apos;rahul.sundararaman@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-38994&quot; title=&quot;Step down on SIGTERM&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-38994&quot;&gt;&lt;del&gt;SERVER-38994&lt;/del&gt;&lt;/a&gt; step down on SIGTERM&lt;/p&gt;

&lt;p&gt;Check to see if we&apos;ve entered shutdown from a shutdown command. If not,&lt;br/&gt;
and if the replication machinery is up, attempt a shutdown in the style&lt;br/&gt;
of a default shutdown command.&lt;/p&gt;

&lt;p&gt;(cherry picked from commit 9f5b13ee93e7eaeafa97ebd1d2d24c66b93cc974)&lt;br/&gt;
Branch: v3.6&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/34217d3b595b172180603e48e17421a330e04a81&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/34217d3b595b172180603e48e17421a330e04a81&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2369764" author="bartle" created="Tue, 13 Aug 2019 23:28:59 +0000"  >&lt;p&gt;Would it be possible to backport this to 3.6 as well?&lt;/p&gt;</comment>
                            <comment id="2190896" author="xgen-internal-githook" created="Mon, 25 Mar 2019 18:29:28 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;email&apos;: &apos;jcarey@argv.me&apos;, &apos;name&apos;: &apos;Jason Carey&apos;, &apos;username&apos;: &apos;hanumantmk&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-38994&quot; title=&quot;Step down on SIGTERM&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-38994&quot;&gt;&lt;del&gt;SERVER-38994&lt;/del&gt;&lt;/a&gt; step down on SIGTERM&lt;/p&gt;

&lt;p&gt;Check to see if we&apos;ve entered shutdown from a shutdown command.  If not,&lt;br/&gt;
and if the replication machinery is up, attempt a shutdown in the style&lt;br/&gt;
of a default shutdown command.&lt;/p&gt;

&lt;p&gt;(cherry picked from commit 9f5b13ee93e7eaeafa97ebd1d2d24c66b93cc974)&lt;br/&gt;
Branch: v4.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/6b5def2ef0f4c798c67a04f390e81aa9f3bb9415&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/6b5def2ef0f4c798c67a04f390e81aa9f3bb9415&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2182331" author="xgen-internal-githook" created="Fri, 15 Mar 2019 22:50:26 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Jason Carey&apos;, &apos;username&apos;: &apos;hanumantmk&apos;, &apos;email&apos;: &apos;jcarey@argv.me&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-38994&quot; title=&quot;Step down on SIGTERM&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-38994&quot;&gt;&lt;del&gt;SERVER-38994&lt;/del&gt;&lt;/a&gt; step down on SIGTERM&lt;/p&gt;

&lt;p&gt;Check to see if we&apos;ve entered shutdown from a shutdown command.  If not,&lt;br/&gt;
and if the replication machinery is up, attempt a shutdown in the style&lt;br/&gt;
of a default shutdown command.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/9f5b13ee93e7eaeafa97ebd1d2d24c66b93cc974&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/9f5b13ee93e7eaeafa97ebd1d2d24c66b93cc974&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2115791" author="milkie" created="Tue, 15 Jan 2019 16:40:23 +0000"  >&lt;blockquote&gt;&lt;p&gt;Unless I&apos;m misunderstanding something, in your first sentence you say &quot;no data is lost&quot;, yet in your second sentence you note that this is in fact not true today with the an &quot;orderly shutdown&quot; via SIGTERM as if a majority of the secondaries have not yet caught up, then data is lost (&quot;rolled back&quot;, which is a misnomer IMO &#8211; committed data is lost). That&apos;s awful behavior, IMO.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;There is some confusion here; I never said &quot;no data is lost&quot;, I said &quot;no committed data is lost&quot;, and it&apos;s an important point. Committed data is never lost; we define &quot;committed&quot; as data that cannot be rolled back.&lt;/p&gt;

&lt;p&gt;Indeed any situation that results in data being rolled back is unfortunate, but such situations only affect users doing writes with write concern less than &quot;w:majority&quot;. Such applications are already in danger of having writes roll back at any moment if there is an unplanned election in the replica set.&lt;/p&gt;

&lt;p&gt;I do believe the shutdown command does a stepdown; we recently fixed some of the default timeout parameters that were used for this code path.&lt;/p&gt;

&lt;p&gt;I&apos;m in favor of proceeding with this ticket, I just want to understand what the proposed solution will be, in light of what behaviors we currently have today.&lt;/p&gt;</comment>
                            <comment id="2115636" author="jason.carey" created="Tue, 15 Jan 2019 15:44:01 +0000"  >&lt;p&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;, I think that&apos;s not correct.  See: &lt;a href=&quot;https://github.com/mongodb/mongo/blob/b489828d0c176e90e47724f6771610227b29f117/src/mongo/db/commands/shutdown_d.cpp#L65-L68&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/blob/b489828d0c176e90e47724f6771610227b29f117/src/mongo/db/commands/shutdown_d.cpp#L65-L68&lt;/a&gt;&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;        &lt;/span&gt;&lt;span style=&quot;color: #006699; font-weight: bold; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;try&lt;/span&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; {&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;            repl::ReplicationCoordinator::get(opCtx)-&amp;gt;stepDown(&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;                opCtx, force, Seconds(timeoutSecs), Seconds(120));&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;        } &lt;/span&gt;&lt;span style=&quot;color: #006699; font-weight: bold; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;catch&lt;/span&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; (&lt;/span&gt;&lt;span style=&quot;color: #006699; font-weight: bold; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;const&lt;/span&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; DBException&amp;amp; e) {&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;Regarding having a longer period where a cluster fails to accept writes, it might be a reasonable compromise to set a timeout + use the force flag to step down.  That way you get something that doesn&apos;t take materially longer than today, but manages a clean handoff when the cluster has little lag.&lt;/p&gt;</comment>
                            <comment id="2115560" author="schwerin" created="Tue, 15 Jan 2019 15:01:49 +0000"  >&lt;p&gt;Note to potential implementers: the shutdown command path does not naturally do a stepdown, today.&lt;/p&gt;</comment>
                            <comment id="2115551" author="matt.lord" created="Tue, 15 Jan 2019 14:58:25 +0000"  >&lt;p&gt;AFAIUI, if you don&apos;t do an election handoff, then it&apos;s handled as a failure by the replicaset &#8211; an election is called for after a majority of the remaining members have no communication with the old primary in the default 10 second window (electionTimeMillis). How can you have a &quot;normal shutdown&quot; that&apos;s at the same time handled as a failure by the overall system?&#160;&lt;/p&gt;

&lt;p&gt;Unless I&apos;m misunderstanding something, in your first sentence you say &quot;no data is lost&quot;, yet in your second sentence you note that this is in fact not necessarily true today with the an &quot;orderly shutdown&quot; via SIGTERM as if a majority of the secondaries have not yet caught up, then locally-but-not-majority-committed data is lost (&quot;rolled back&quot;, which is a bit misnomer&#160;IMO). Side note: This is the default behavior today as w:majority is not the default, and it&apos;s bad default behavior, IMO. I would prefer we always choose data safety over performance by default and let production engineers and DBAs explicitly choose when to prefer performance over safety.&#160;&lt;/p&gt;

&lt;p&gt;Imagine a not-too-uncommon case where a user believes that machine failures are very rare events for them and they don&apos;t wish to take the constant write latency penalty of w:majority and are OK with the trade-off of potentially losing the last N writes when the rare failure occurs. I guess that they would be very (unpleasantly) surprised to learn that in practice many &quot;planned maintenance&quot; operations&#160;are in effect treated as machine failures too.&#160;&lt;/p&gt;</comment>
                            <comment id="2115536" author="milkie" created="Tue, 15 Jan 2019 14:52:59 +0000"  >&lt;p&gt;I would argue that the normal shutdown does indeed do an election handoff, it&apos;s just not as fast as it could be. The replication subsystem does not handle the shutdown as a failure; everything operates as designed: No committed data is lost and no data is corrupted.&lt;/p&gt;

&lt;p&gt;Arguably, some users may prefer the current behavior, since introducing a stepdown as part of SIGTERM handling can potentially expand the window of time where a cluster will not accept writes, since the primary will now wait for a majority of secondaries to catch up during stepdown in an attempt to protect as many writes as possible from being rolled back.&lt;/p&gt;</comment>
                            <comment id="2115526" author="matt.lord" created="Tue, 15 Jan 2019 14:46:08 +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;,&#160;I would argue that if the normal shutdown &#8211; and SIGTERM is a normal/standard shutdown method &#8211;&#160;doesn&apos;t do an election handoff, and the replication subsystem thus treats/handles the shutdown as a &lt;b&gt;failure&lt;/b&gt;, then it&apos;s not clean. It&apos;s clean as far as the single node storage subsystem is concerned, we know that. But as a distributed database, I would argue that the collective replication and storage system is just as important.&#160;&lt;/p&gt;

&lt;p&gt;What am I missing?&#160;&lt;/p&gt;</comment>
                            <comment id="2115510" author="milkie" created="Tue, 15 Jan 2019 14:39:05 +0000"  >&lt;p&gt;I&apos;m not sure why this is a bug.  Upon the receipt of any of SIGHUP, SIGINT, SIGTERM, or SIGXCPU, the server shuts down cleanly.  (In contrast, the server shuts down uncleanly on receipt of SIGKILL.) &lt;br/&gt;
Making election handoff more efficient in the face of terminal signals is a worthy goal, but it is an Improvement.&lt;br/&gt;
Also, we should consider Windows here, since it already has a different exit path for this type of thing, and it would be weird if Windows didn&apos;t do election handoff yet Linux did.&lt;/p&gt;</comment>
                            <comment id="2114968" author="matt.lord" created="Mon, 14 Jan 2019 22:45:35 +0000"  >&lt;p&gt;I&apos;d prefer we treat this as a bug (changing Type for now) and backport it to at least 4.0, as a `&lt;tt&gt;kill &lt;span class=&quot;error&quot;&gt;&amp;#91;-15&amp;#93;&lt;/span&gt;&#160;&amp;lt;PID&amp;gt;&lt;/tt&gt;` is generally considered a standard way to terminate a process properly &#8211; 1) that&apos;s generally what is done in SysV init scripts, and in fact &lt;a href=&quot;https://github.com/mongodb/mongo/blob/master/rpm/init.d-mongod#L103&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;that&apos;s what ours does&lt;/a&gt; 2) that&apos;s what &lt;a href=&quot;https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStop=&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;systemd does without an explicit &lt;tt&gt;ExecStop&lt;/tt&gt; option&lt;/a&gt;, which &lt;a href=&quot;https://github.com/mongodb/mongo/blob/master/rpm/mongod.service&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;we don&apos;t specify&lt;/a&gt; &#8211;&#160;so we really should effectively take the same steps we do for &lt;a href=&quot;https://docs.mongodb.com/manual/reference/command/shutdown/#dbcmd.shutdown&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;the shutdown command&lt;/a&gt;. Having different shutdown paths is a breeding ground for many subtle bugs and unexpected behaviors &#8211; with the noted issue for&#160;our own Kubernetes operator being a critical example.&#160;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10420">
                    <name>Backports</name>
                                            <outwardlinks description="backported by">
                                                        </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                                                <inwardlinks description="is documented by">
                                        <issuelink>
            <issuekey id="720241">DOCS-12561</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="274378">SERVER-23293</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10520">
                    <name>Problem/Incident</name>
                                            <outwardlinks description="causes">
                                        <issuelink>
            <issuekey id="720416">SERVER-40252</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is caused by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="685557">SERVER-39424</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12.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_12450" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Backport Requested</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="15640"><![CDATA[v4.0]]></customfieldvalue>
    <customfieldvalue key="15141"><![CDATA[v3.6]]></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>Mon, 14 Jan 2019 22:45:35 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        4 years, 19 weeks, 5 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-1273</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, 19 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_16465" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Linked BF Score</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>50.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>alyson.cabral@mongodb.com</customfieldvalue>
            <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>bartle</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>matt.lord</customfieldvalue>
            <customfieldvalue>mira.carey@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hujaf3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hu99av:</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="2856">Service Arch 2019-03-11</customfieldvalue>
    <customfieldvalue id="2857">Service Arch 2019-03-25</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|huiwof:</customfieldvalue>

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