<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 07:50:05 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>[DOCS-5324] Document how to use findAndModify with write concern to achieve &quot;quorum read&quot; behavior</title>
                <link>https://jira.mongodb.org/browse/DOCS-5324</link>
                <project id="10380" key="DOCS">Documentation</project>
                    <description>&lt;p&gt;Per discussion in the comments of &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-17975&quot; title=&quot;Stale reads with WriteConcern Majority and ReadPreference Primary&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-17975&quot;&gt;&lt;del&gt;SERVER-17975&lt;/del&gt;&lt;/a&gt;, in MongoDB systems since at least 2.6, one can use findAndModify with a &quot;w:majority&quot; write concern to perform a read of data that cannot be rolled back and is not stale. We should document this technique for users that require it.&lt;/p&gt;

&lt;p&gt;Highlights of the technique:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;The findAndModify must use exact match satisfiable with an existing unique index.&lt;/li&gt;
	&lt;li&gt;The findAndModify must modify some field in the document.  I recommend using $inc to increment a field with a name like {{ _&lt;em&gt;dummy_counter&lt;/em&gt;_}}.&lt;/li&gt;
	&lt;li&gt;The write concern used with the findAndModify must be w:majority&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Caveats: Not all drivers support findAndModify with write concern.&lt;/p&gt;</description>
                <environment></environment>
        <key id="201360">DOCS-5324</key>
            <summary>Document how to use findAndModify with write concern to achieve &quot;quorum read&quot; behavior</summary>
                <type id="5" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14716&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="201363">DOCS-5326</parent>
                                    <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="9">Done</resolution>
                                        <assignee username="kyle.suarez@mongodb.com">Kyle Suarez</assignee>
                                    <reporter username="schwerin@mongodb.com">Andy Schwerin</reporter>
                        <labels>
                            <label>3.2</label>
                    </labels>
                <created>Thu, 30 Apr 2015 20:12:25 +0000</created>
                <updated>Wed, 2 Nov 2016 19:51:24 +0000</updated>
                            <resolved>Thu, 14 Jan 2016 21:29:27 +0000</resolved>
                                                    <fixVersion>mongodb-3.1.x</fixVersion>
                                    <component>Server</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>14</watches>
                                                                                                                <comments>
                            <comment id="1338340" author="emily.hall" created="Wed, 27 Jul 2016 19:09:53 +0000"  >&lt;p&gt;Closed for housekeeping on 7/27/2016 by Emily Hall. &lt;br/&gt;
If you require additional support, please open a new ticket for prioritization. &lt;br/&gt;
Thanks,&lt;br/&gt;
Emily&lt;/p&gt;</comment>
                            <comment id="1135421" author="xgen-internal-githook" created="Thu, 14 Jan 2016 21:24:11 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ksuarz&apos;, u&apos;name&apos;: u&apos;Kyle Suarez&apos;, u&apos;email&apos;: u&apos;kyle.suarez@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; clarify findAndModify quorum read doc&lt;/p&gt;

&lt;p&gt;This explicitly details the reasons why one would require a &quot;quorum read&quot; over&lt;br/&gt;
the existing majority and local read concerns. It also adds a note warning that&lt;br/&gt;
this procedure is much more expensive than a regular read.&lt;/p&gt;

&lt;p&gt;This commit also fixes some grammar and explicitly mentions that this technique&lt;br/&gt;
is new in MongoDB 3.2.&lt;/p&gt;

&lt;p&gt;Signed-off-by: kay &amp;lt;kay.kim@10gen.com&amp;gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/3043f5cd5483a878862342e0431d65e78491e318&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/3043f5cd5483a878862342e0431d65e78491e318&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1135420" author="xgen-internal-githook" created="Thu, 14 Jan 2016 21:24:10 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;ksuarz&apos;, u&apos;name&apos;: u&apos;Kyle Suarez&apos;, u&apos;email&apos;: u&apos;kyle.suarez@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; no gle for findAndModify quorum reads&lt;/p&gt;

&lt;p&gt;Rather than issuing a getLastError, you can use a write concern of ``majority``&lt;br/&gt;
to ensure that findAndModify reads only data that cannot be rolled back.&lt;/p&gt;

&lt;p&gt;Signed-off-by: kay &amp;lt;kay.kim@10gen.com&amp;gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/c16563bf83a5883a311b2868aa272643a7b4546f&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/c16563bf83a5883a311b2868aa272643a7b4546f&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1135419" author="xgen-internal-githook" created="Thu, 14 Jan 2016 21:24:09 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&lt;/p&gt;

&lt;p&gt;This cherry-picks 046152322b4fae3a98835ed74b718ef7d88f6da2 to apply it again,&lt;br/&gt;
undoing the reversion in cf6ab08992633803fa79ee8d8a863200bea435fa.&lt;/p&gt;

&lt;p&gt;The changes in source/reference/write-concern.txt have been ignored in favor of&lt;br/&gt;
more recent changes.&lt;/p&gt;

&lt;p&gt;Signed-off-by: kay &amp;lt;kay.kim@10gen.com&amp;gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/1d060d0dbc451b30c64bd57d1bc07761b85ff51e&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/1d060d0dbc451b30c64bd57d1bc07761b85ff51e&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1129988" author="david.golden" created="Fri, 8 Jan 2016 19:47:22 +0000"  >&lt;p&gt;I think you might want to address how this is different than readConcern &lt;tt&gt;level:majority&lt;/tt&gt;.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;read concern &lt;tt&gt;level:majority&lt;/tt&gt; against a primary ensures data that won&apos;t roll back, but it could be stale in a small window of time when the primary is partitioned and hasn&apos;t stepped down yet.&lt;/li&gt;
	&lt;li&gt;findAndModify with write concern &lt;tt&gt;w:majority&lt;/tt&gt; can only succeed with a primary that is on the majority side of a partition, thus it ensures that the read is not stale.  (The downside being write latency rather than read latency.)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;More specifically, the opening paragraph is a bit confusing.  I also think it&apos;s important to caveat that this technique has a substantial cost over read concern &lt;tt&gt;level::majority&lt;/tt&gt; and should only be used when staleness is absolutely unacceptable.&lt;/p&gt;

&lt;p&gt;You have:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;When reading from replica sets, in some edge cases, clients can read stale data even when specifying a primary read preference. Clients may also see results of writes before they are made durable and before they have propagated to enough replica set members to avoid rollbacks.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I would phrase it more like this:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;When reading from a replica set primary using a local read concern(link), clients may see results of writes before they are made durable and before they have propagated to enough replica set members to avoid rollbacks.  This can be prevented by reading from a primary with read concern majority(link).  However, even with read concern majority, during a partition it is still possible for a client to read stale data if the primary is on the minority side and has not yet stepped down.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Then the next paragraph opens &quot;This tutorial outlines a procedure...&quot; which directly addresses how I left the opening paragraph.&lt;/p&gt;

&lt;p&gt;Then before the &quot;Prerequisites&quot; paragraph is probably the right place to put the caveat about the latency cost of turning a read into a write.&lt;/p&gt;</comment>
                            <comment id="1125670" author="milkie" created="Mon, 4 Jan 2016 20:55:27 +0000"  >&lt;p&gt;Rescoped to version 3.2 of the manual only.  In version 3.2 it should be possible to use the findAndModify technique as documented.&lt;/p&gt;</comment>
                            <comment id="910088" author="xgen-internal-githook" created="Mon, 11 May 2015 16:18:22 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit 98a314ff56bdec972970f633cdcbc118182bc98c.&lt;br/&gt;
Branch: v2.6&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/36b44d72ab52bedc5e67ba8f36ca57c71832cef8&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/36b44d72ab52bedc5e67ba8f36ca57c71832cef8&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="910083" author="xgen-internal-githook" created="Mon, 11 May 2015 16:16:13 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit 046152322b4fae3a98835ed74b718ef7d88f6da2.&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/cf6ab08992633803fa79ee8d8a863200bea435fa&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/cf6ab08992633803fa79ee8d8a863200bea435fa&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="910076" author="xgen-internal-githook" created="Mon, 11 May 2015 16:12:51 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit fc5e1bd7d9081791940a00e538b224db8903653f.&lt;br/&gt;
Branch: v2.4&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/f162de8b7bcfc864e28b589ee98d6f48666fed86&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/f162de8b7bcfc864e28b589ee98d6f48666fed86&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="910074" author="xgen-internal-githook" created="Mon, 11 May 2015 16:12:31 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: Revert &quot;&lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&quot;&lt;/p&gt;

&lt;p&gt;This reverts commit fc5e1bd7d9081791940a00e538b224db8903653f.&lt;br/&gt;
Branch: v24&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/f162de8b7bcfc864e28b589ee98d6f48666fed86&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/f162de8b7bcfc864e28b589ee98d6f48666fed86&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="910070" author="shannon.bradshaw@10gen.com" created="Mon, 11 May 2015 16:10:33 +0000"  >&lt;p&gt;Raised in the driver leads meeting this morning, &quot;I don&apos;t think you can really do this with any driver yet, since both ops have to be on the same socket.&quot;. &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kay.kim%4010gen.com&quot; class=&quot;user-hover&quot; rel=&quot;kay.kim@10gen.com&quot;&gt;kay.kim@10gen.com&lt;/a&gt; let&apos;s unpublish this. We need to determine whether any drivers actually support this. If they don&apos;t, our proposed solution is misleading.&lt;/p&gt;</comment>
                            <comment id="909210" author="xgen-internal-githook" created="Fri, 8 May 2015 22:27:42 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&lt;br/&gt;
Branch: v2.4&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/fc5e1bd7d9081791940a00e538b224db8903653f&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/fc5e1bd7d9081791940a00e538b224db8903653f&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="909193" author="xgen-internal-githook" created="Fri, 8 May 2015 22:12:40 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&lt;br/&gt;
Branch: v2.6&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/98a314ff56bdec972970f633cdcbc118182bc98c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/98a314ff56bdec972970f633cdcbc118182bc98c&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="909192" author="xgen-internal-githook" created="Fri, 8 May 2015 22:12:01 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&lt;br/&gt;
Branch: v2gs&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/98a314ff56bdec972970f633cdcbc118182bc98c&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/98a314ff56bdec972970f633cdcbc118182bc98c&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="909188" author="xgen-internal-githook" created="Fri, 8 May 2015 22:08:30 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;kay-kim&apos;, u&apos;name&apos;: u&apos;kay&apos;, u&apos;email&apos;: u&apos;kay.kim@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DOCS-5324&quot; title=&quot;Document how to use findAndModify with write concern to achieve &amp;quot;quorum read&amp;quot; behavior&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DOCS-5324&quot;&gt;&lt;del&gt;DOCS-5324&lt;/del&gt;&lt;/a&gt; quorum reads with findAndModify&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/docs/commit/046152322b4fae3a98835ed74b718ef7d88f6da2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/docs/commit/046152322b4fae3a98835ed74b718ef7d88f6da2&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="195242">SERVER-17975</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>15.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 6 May 2015 23:57:20 +0000</customfieldvalue>

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


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>jess.mokrzecki@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            7 years, 29 weeks ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>david.golden@mongodb.com</customfieldvalue>
            <customfieldvalue>emily.hall</customfieldvalue>
            <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>kyle.suarez@mongodb.com</customfieldvalue>
            <customfieldvalue>shannon.bradshaw</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrqddj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hs8xbz:</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_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrz19j:</customfieldvalue>

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