<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:49:38 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-19043] Implement a connectDatabase / disconnectDatabase functionality.</title>
                <link>https://jira.mongodb.org/browse/SERVER-19043</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;With the old engine, you could shift folders/files in and out and they would become immediately available for access from clients. &lt;br/&gt;
This was a great way to manage large data importing / index rebuilding. You could take a single server offline - build new data/indexes and then systematically copy this structure around ones replicaset to get them back into sync - oplog - didnt come into it.&lt;br/&gt;
With WiredTiger engine, this will not work, as if you create a new database/folder or increase the collection count within that database - it is ignored. &lt;br/&gt;
I believe because the underlying structure is not generated to support the new files.&lt;/p&gt;

&lt;p&gt;Is it possible to generate this missing structure simply by issueing a command which would then parse the file structure to rebuild its internal mappings.&lt;/p&gt;

&lt;p&gt;Hope that explains the requirement. Sorry if this request is already somewhere else - its a little fiddly to find through Jira.&lt;/p&gt;</description>
                <environment>Windows for me, but probably the other places.</environment>
        <key id="211459">SERVER-19043</key>
            <summary>Implement a connectDatabase / disconnectDatabase functionality.</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</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="9">Done</resolution>
                                        <assignee username="brian.lane@mongodb.com">Brian Lane</assignee>
                                    <reporter username="paul.reed">Paul Reed</reporter>
                        <labels>
                            <label>asya</label>
                    </labels>
                <created>Thu, 18 Jun 2015 08:15:39 +0000</created>
                <updated>Fri, 21 Aug 2020 05:36:51 +0000</updated>
                            <resolved>Fri, 21 Aug 2020 05:36:50 +0000</resolved>
                                                                    <component>Admin</component>
                    <component>WiredTiger</component>
                                        <votes>14</votes>
                                    <watches>26</watches>
                                                                                                                <comments>
                            <comment id="3351657" author="brian.lane" created="Fri, 21 Aug 2020 05:36:38 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed%40gprxdata.com&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed@gprxdata.com&quot;&gt;paul.reed@gprxdata.com&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;As we discussed, I will go ahead and close this issue as gone away.  As you continue to experiment with mtransfer, feel free to reach out to me directly if you have questions or encounter any problems.&lt;/p&gt;</comment>
                            <comment id="2881620" author="brian.lane" created="Tue, 18 Feb 2020 04:46:03 +0000"  >&lt;p&gt;We have recently released an updated version of &lt;a href=&quot;https://github.com/rueckstiess/mtools&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mtools&lt;/a&gt;, which includes a new tool called &lt;a href=&quot;http://blog.rueckstiess.com/mtools/mtransfer.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mtransfer&lt;/a&gt; that should help address some of the requirements raised in this issue.  &lt;/p&gt;

&lt;p&gt;We have currently flagged it as experimental as we gather feedback. Feel free to reach out to me directly via brian.lane@mongodb.com if you encounter any issues getting mtools setup in your environment or have any feedback regarding mtransfer.&lt;/p&gt;
</comment>
                            <comment id="2470396" author="brian.lane" created="Tue, 8 Oct 2019 05:02:52 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed%40gprxdata.com&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed@gprxdata.com&quot;&gt;paul.reed@gprxdata.com&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;Unfortunately not.  I will reach out to you via email to set up a meeting to discuss.&lt;/p&gt;

&lt;p&gt;I want to get you to a later version w/ WiredTiger, but don&apos;t want this issue to be the blocker.&lt;/p&gt;

&lt;p&gt;-Brian&lt;/p&gt;</comment>
                            <comment id="2448355" author="paul.reed@gprxdata.com" created="Wed, 2 Oct 2019 19:37:11 +0000"  >&lt;p&gt;Status is still Open on this one. Is there any movement forward with a solution which would work, and thus allow me to move to the latest version.&lt;/p&gt;

&lt;p&gt;Any update ?&lt;/p&gt;</comment>
                            <comment id="2243426" author="mhughes" created="Sat, 11 May 2019 09:24:43 +0000"  >&lt;p&gt;On WT here with version 3.6.12 and would very much like to see this functionality, in 3.6 if possible as we are not ready to move to 4.x. I have terabytes of data and cannot dump to the destination and import due to storage restrictions, was very surprised to see this is not possible. This would be invaluable in recovery situations.&lt;/p&gt;</comment>
                            <comment id="2221666" author="paul.reed" created="Tue, 23 Apr 2019 12:11:35 +0000"  >&lt;p&gt;Currently we are sitting at : MongoDB server version: 3.6.2 on the MMAPv1.&lt;/p&gt;

&lt;p&gt;This is the only issue at the moment preventing us moving to WT. The worry of corruption requiring a full architecture rebuild as noticed in some posts ( maybe in the past and not current ) is also a worry, however, the mechanics with directory backups somewhat negate that risk as well as allow us greater data update management.&lt;/p&gt;

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

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="2221429" author="brian.lane" created="Tue, 23 Apr 2019 05:41:19 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed&quot;&gt;paul.reed&lt;/a&gt;, I can&apos;t make a guarantee at this time regarding implementation.  However, we have made some changes in the 4.2 release with backup cursors that could make the work required here potentially not as bad.&lt;/p&gt;

&lt;p&gt;What version of the server are you currently using?  I assume you are still with MMAPv1 as well?  Is this the main issue preventing you from migrating to a newer version w/ WiredTiger?&lt;/p&gt;

&lt;p&gt;-Brian&lt;/p&gt;</comment>
                            <comment id="2214258" author="paul.reed" created="Mon, 15 Apr 2019 20:47:27 +0000"  >&lt;p&gt;Or at the least allow for the metadata of a database to reside in the db folder (therefore allowing folder copying) &lt;/p&gt;</comment>
                            <comment id="2214254" author="paul.reed" created="Mon, 15 Apr 2019 20:44:55 +0000"  >&lt;p&gt;Just seen you&apos;ve changed status. Please please please implement this. &lt;/p&gt;</comment>
                            <comment id="1938852" author="paul.reed" created="Wed, 4 Jul 2018 17:03:32 +0000"  >&lt;p&gt;Please can you revisit this item now that &lt;ins&gt;&lt;b&gt;MMAPv is deprecated&lt;/b&gt;&lt;/ins&gt;.&lt;/p&gt;</comment>
                            <comment id="1598390" author="chris.kuethe@gmail.com" created="Thu, 15 Jun 2017 18:48:57 +0000"  >&lt;p&gt;This would also be helpful for emergency recovery situations: copy in the database directory to the root of a new dbpath, start up a new server, and attach and repair it.&lt;/p&gt;</comment>
                            <comment id="1442614" author="kmanchev@epo.org" created="Sat, 26 Nov 2016 10:16:10 +0000"  >&lt;p&gt;I do not understand how such critical issue has  only 9 votes up to now with mine from today ... , please, consider this seems to be a serious limitation in flexibility in MongoDB/WiredTiger ...&lt;/p&gt;</comment>
                            <comment id="1257157" author="yfinkelstein" created="Thu, 5 May 2016 22:34:24 +0000"  >&lt;p&gt;I can&apos;t agree more with Paul. No matter how great are WT concurrency improvements are, the fact is that when one was able to build an image of a database offline on another machine, upload the entire directory to every member of the replica set, and just &quot;activate&quot; it by telling application to start writes to this database it was 100 times more efficient and predictable compared to mongorestore. For one, the secondaries don&apos;t need to replicate the new DB which is the case with mongorestore!  The user can throttle the process of file copying to RS members and achieve smooth and predictable outcome.  I just don&apos;t understand why mongodb is not seeing the merits of this process and instead is trying to convince customers than WT is better than mmapv1. This issue is not at all about what engine is better. &lt;/p&gt;</comment>
                            <comment id="1127528" author="dan@10gen.com" created="Wed, 6 Jan 2016 15:33:07 +0000"  >&lt;p&gt;Hi Paul,&lt;br/&gt;
So, the concurrency improvements with WT may make your old approach unnecessary, though overall data throughput could cause service interruptions as well simply by writing a lot of data into your production environment.  I can&apos;t say from here.&lt;/p&gt;

&lt;p&gt;A couple questions:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;What version did you see db-level locking with large aggregations?  Collection-level locking was introduced in v3.0.&lt;/li&gt;
	&lt;li&gt;Are you using $out with agg?  In order to create the output collection, it will take a db-level lock, but only for a very short period of time.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Also, there is the possibility that you could continue doing your processing on the side and simply use &lt;tt&gt;mongorestore&lt;/tt&gt; to import the data into your prod servers.  There are a few knobs you can use to control the level of concurrency, and thus load, with this approach.&lt;/p&gt;</comment>
                            <comment id="1126493" author="paul.reed" created="Tue, 5 Jan 2016 17:01:10 +0000"  >&lt;p&gt;Thanks for replying.&lt;/p&gt;

&lt;p&gt;I am inferring the issue from experiences with users being locked out of access through MMAPv1.&lt;/p&gt;

&lt;p&gt;I need to rebuild sandbox areas from datasnapshots 2 or 3 times a month from subsets of imported data. I have found that aggregation on large datasets will cause locking at db level, which causes our users to block on reads. Also, the large rebuild, which by necessity drops and recreates grouped up data, including lengthy index builds, would cause areas of data to go missing from sight. I suppose building into a temporary database and then swapping users to it in a versioned sort of way might be the work around, which I have not tried. &lt;br/&gt;
I take it that renaming databases is still a painful process regardless of engine - so maybe this is not even a goer.&lt;/p&gt;

&lt;p&gt;The sheer convenience of backup and restore processes based on directory level copy was a massive factor in our using Mongo as our data store. &lt;br/&gt;
I guess I will just need to continue with MM for the foreseeable future. I trust you are not planning on decomissioning that engine ?&lt;/p&gt;

&lt;p&gt;Paul&lt;/p&gt;</comment>
                            <comment id="1126424" author="dan@10gen.com" created="Tue, 5 Jan 2016 16:02:48 +0000"  >&lt;p&gt;Hi Paul, I understand your use case but this is not a small change to WiredTiger and the MongoDB integration layer and we have no immediate plans to add this feature to MongoDB with WiredTiger.  Have you tested the impact of the data import on your system with WiredTiger, or are you inferring the issue from experience with MMAPv1?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Dan&lt;/p&gt;</comment>
                            <comment id="1126320" author="paul.reed" created="Tue, 5 Jan 2016 14:28:22 +0000"  >&lt;p&gt;Any further thoughts on this: really would love for the meta to be stored in the database directory when directory level databases are enabled. &lt;/p&gt;
</comment>
                            <comment id="1104147" author="paul.reed" created="Thu, 3 Dec 2015 09:44:32 +0000"  >&lt;p&gt;I wonder if there is any further thoughts on adding this re-sync meta process to allow for folder migration in and out of the WiredTiger engine. I am desperate to get to the benefits of being able to copy collection level files around replicasets (at the moment I copy the entire database with the MM engine, which is ok - but could be optimised better at collection level with WT) and also to get the speed benefits from WT.&lt;br/&gt;
Updating the entire replicaset with my group/index rebuilds really is not an option for me as it takes the system offline effectively for over 12 hours.&lt;/p&gt;
</comment>
                            <comment id="997623" author="ramon.fernandez" created="Wed, 5 Aug 2015 20:24:48 +0000"  >&lt;p&gt;There is currently no process to manually move files around or recreate the necessary metadata when using the WiredTiger engine. This ticket remains open to consider this functionality in future releases.&lt;/p&gt;

&lt;p&gt;Cheers,&lt;br/&gt;
Ram&#243;n.&lt;/p&gt;</comment>
                            <comment id="995867" author="paul.reed" created="Tue, 4 Aug 2015 11:27:48 +0000"  >&lt;p&gt;So is there a process currently, or could there be a process to force the rebuild of this meta. Or possibly could the meta be stored in the directory - for directory based databases - and therefore folder copy would be doable again ?&lt;br/&gt;
This is a massive negative for me to not be able to manage with folders, i.e. to allow fallback to old snapshot in the event of corruption - or implement offline data import routines.&lt;/p&gt;</comment>
                            <comment id="993456" author="michael.cahill" created="Fri, 31 Jul 2015 00:56:35 +0000"  >&lt;p&gt;This procedure won&apos;t work with WiredTiger regardless of &lt;tt&gt;sizeStorer&lt;/tt&gt;: &quot;copying over the database folder&quot; will just lead to corruption because the WiredTiger metadata won&apos;t match the files.&lt;/p&gt;</comment>
                            <comment id="992864" author="ramon.fernandez" created="Thu, 30 Jul 2015 13:43:26 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed&quot;&gt;paul.reed&lt;/a&gt;, my guess is that the moment your primary takes a single write operation during this process the &lt;tt&gt;sizeStorer.wt&lt;/tt&gt; file may become out of sync (I&apos;m also guessing this may happen after a checkpoint too), which would negate the benefits of the procedure.&lt;/p&gt;

&lt;p&gt;I&apos;ll let others with more WiredTiger knowledge comment, but in the meantime if you&apos;re to try this procedure I&apos;d strongly recommend you do it in a test setup.&lt;/p&gt;</comment>
                            <comment id="992835" author="paul.reed" created="Thu, 30 Jul 2015 13:10:27 +0000"  >&lt;p&gt;If I did this, would it work around the metadata missing problem:&lt;/p&gt;

&lt;p&gt;1) Against RS: create new database ( create all new possible collections with a {} insert )&lt;br/&gt;
2) Wait for sync&lt;br/&gt;
3) Take Secondary offline&lt;br/&gt;
4) Open standalone instance - perform massive import, drop collections, recreate collections, generate indexes.&lt;br/&gt;
5) Cycle RS servers, copying over the database folder with the one from the standalone.&lt;br/&gt;
6) Bring RS back up.&lt;/p&gt;</comment>
                            <comment id="992834" author="paul.reed" created="Thu, 30 Jul 2015 13:10:22 +0000"  >
&lt;p&gt;What information is stored in the metadata ?&lt;br/&gt;
If it does contain machine specific information, then possibly the solution/requirement would be to store this information also within the folder itself and then on startup to scan folders for this metadata and appropriate this back into dbpath ?&lt;/p&gt;</comment>
                            <comment id="945345" author="ramon.fernandez" created="Fri, 19 Jun 2015 12:26:29 +0000"  >&lt;p&gt;Thanks for the additional information &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed&quot;&gt;paul.reed&lt;/a&gt;. Apologies if I wasn&apos;t clear: we do not consider this a WiredTiger issue because is not about using WiredTiger stand-alone, but as a storage engine inside MongoDB. If you are using WiredTiger without MongoDB then we should move this ticket back to the WT project, but as long as is related to MongoDB it should remain in SERVER with the rest of the MongoDB issues. Hope that clarifies things.&lt;/p&gt;

&lt;p&gt;WiredTiger keeps additional metadata in files inside &lt;tt&gt;dbpath&lt;/tt&gt;, so as you&apos;ve found collection files are not detected when dropped in. I&apos;m tagging this ticket as &quot;Needs Triage&quot; for further consideration.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Ram&#243;n.&lt;/p&gt;</comment>
                            <comment id="945193" author="paul.reed" created="Fri, 19 Jun 2015 05:42:06 +0000"  >&lt;p&gt;Well: &lt;br/&gt;
2 times a month I run a dataimport which takes 7 hours to complete. It would have a detrimental effect on performance if it was writing to primary. &lt;br/&gt;
So I take a secondary offline, run the import into a new collection, copy the collection to all remaining servers in preparation for &quot;move&quot;ing the folder into the data path, this move then takes the rolling servers offline for the minimum amount of time. There is little oplog involvement.&lt;br/&gt;
Seven hours is a long time for an intense data import, and some core static data is changed over that time. So - just in case, on the building we snapshot data out by zipping away copies of folders. Its quicker to get back up from copies rather than rebuilding.&lt;br/&gt;
I believe various FAQ/tips  in the mongo docs advise this approach.&lt;br/&gt;
I fail to see really how this is not a WiredT issue.&lt;/p&gt;</comment>
                            <comment id="945011" author="ramon.fernandez" created="Thu, 18 Jun 2015 23:31:22 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=paul.reed&quot; class=&quot;user-hover&quot; rel=&quot;paul.reed&quot;&gt;paul.reed&lt;/a&gt;, I&apos;ve moved this ticket to the SERVER project, as my understanding of your description is that this is really a MongoDB issue.&lt;/p&gt;

&lt;p&gt;Can you please elaborate on the &quot;shift folders/files&quot; part of your description above and provide a recipe/scenario where this was handy in the past? That should help us understand your suggestion better.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Ram&#243;n.&lt;/p&gt;

&lt;p&gt;PS: yes, some times is hard to find things in JIRA &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="943902" author="paul.reed" created="Thu, 18 Jun 2015 08:20:59 +0000"  >&lt;p&gt;Also - folder copying very easily created a fallback safety net - for sensitive operations. This would be even better with the WT way of naming files based around the collection - rather than the database.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="277927">SERVER-23573</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="392654">SERVER-29557</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="410907">SERVER-30452</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>28.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000Up9eLIAR, 500A000000cDne6IAC]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 18 Jun 2015 23:25:06 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        3 years, 24 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_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>brian.lane@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            3 years, 24 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>brian.lane@mongodb.com</customfieldvalue>
            <customfieldvalue>chris.kuethe@gmail.com</customfieldvalue>
            <customfieldvalue>dan@mongodb.com</customfieldvalue>
            <customfieldvalue>kmanchev@epo.org</customfieldvalue>
            <customfieldvalue>mhughes</customfieldvalue>
            <customfieldvalue>michael.cahill@mongodb.com</customfieldvalue>
            <customfieldvalue>paul.reed</customfieldvalue>
            <customfieldvalue>paul.reed@gprxdata.com</customfieldvalue>
            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>
            <customfieldvalue>yfinkelstein</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrl2sv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr7h7b:</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_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|hrlhin:</customfieldvalue>

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