<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:24:15 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-10860] Mongos process is consuming more swap memory </title>
                <link>https://jira.mongodb.org/browse/SERVER-10860</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I am facing an issue related to the mongos process in my setup, mongos process is consuming more amount of swap memory, initially when I start the mongos process it consumes around 150-300MB of swap memory. After that i start provision data to the database, sometime later I observed mongos process is consumes around 4 GB of swap memory (swap memory which is configured to the Linux machine is 4.1GB), consumes almost all swap memory configured in setup.&lt;/p&gt;

&lt;p&gt;Configuration of my setup is below.&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Created 3 replica-sets which having 5 members each including arbiter&lt;/li&gt;
	&lt;li&gt;Created 3 config servers&lt;/li&gt;
	&lt;li&gt;Created the 32 mongos servers.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Each mongod and mongos processes are running in individual Linux machine. &lt;/p&gt;

&lt;p&gt;Steps which i followed to recover swap &lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Stop mongos process&lt;/li&gt;
	&lt;li&gt;Start mongos process&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;After that consumption of swap memory reduce and consuming 150-300MB of swap.&lt;/p&gt;

&lt;p&gt;Could you please suggest?&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya&lt;/p&gt;</description>
                <environment>Linux CentOs 5.8</environment>
        <key id="91221">SERVER-10860</key>
            <summary>Mongos process is consuming more swap memory </summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="1" iconUrl="https://jira.mongodb.org/images/icons/priorities/blocker.svg">Blocker - P1</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="-1">Unassigned</assignee>
                                    <reporter username="kthummur">Krishnachaitanya Thummuru</reporter>
                        <labels>
                            <label>sharding</label>
                    </labels>
                <created>Tue, 24 Sep 2013 08:32:02 +0000</created>
                <updated>Mon, 11 Jul 2016 17:38:02 +0000</updated>
                            <resolved>Sat, 5 Apr 2014 06:50:04 +0000</resolved>
                                    <version>2.4.1</version>
                                                    <component>Sharding</component>
                                        <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="536711" author="kthummur" created="Sat, 5 Apr 2014 05:47:52 +0000"  >&lt;p&gt;Hi Thomas,&lt;/p&gt;

&lt;p&gt;Thanks for update!&lt;/p&gt;

&lt;p&gt;I had followed the all the steps recommend for the NUMA hardware.&lt;/p&gt;

&lt;p&gt;Consumption of more swap memory of mongos process is resolved after upgrade to the 2.4.6, and as per Mike comments the mongod swap consumption fixed in the new build 2.4.7. for current even though mongod is taking more swap memory it not effecting much.&lt;/p&gt;

&lt;p&gt;Please close the ticket.&lt;/p&gt;

&lt;p&gt;Thanks for your support!&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya  &lt;/p&gt;</comment>
                            <comment id="536179" author="thomasr" created="Fri, 4 Apr 2014 19:53:12 +0000"  >&lt;p&gt;Hi Krishnachaitanya,&lt;/p&gt;

&lt;p&gt;I noticed this issue is still unresolved and wanted to follow up with you. Have you confirmed that your NUMA is running with an interleave memory policy (i.e. &lt;tt&gt;--interleave=all&lt;/tt&gt;) as per our &lt;a href=&quot;http://docs.mongodb.org/manual/administration/production-notes/#mongodb-and-numa-hardware&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;recommendations for NUMA hardware&lt;/a&gt;? Is the swapping still an issue for you? Please let us know if we can close the ticket.&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Thomas&lt;/p&gt;</comment>
                            <comment id="469142" author="kthummur" created="Wed, 11 Dec 2013 11:08:41 +0000"  >&lt;p&gt;Hi Mike,&lt;/p&gt;

&lt;p&gt;Thank you for the link &lt;br/&gt;
yes we are followed the steps mentioned in the document to create the setup and I verified the system parameter with the system parameters mentioned in the documentation and system parameters are looks similar as present in the documentation.&lt;/p&gt;

&lt;p&gt;Will verify configuration one more time and let you know.&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya &lt;/p&gt;</comment>
                            <comment id="468128" author="michael.grundy@10gen.com" created="Mon, 9 Dec 2013 21:13:32 +0000"  >&lt;p&gt;Hi Krishnachaitanya -&lt;/p&gt;

&lt;p&gt;I should have thought of this earlier. You&apos;re running on NUMA hardware. Have you reviewed this documentation? &lt;a href=&quot;http://docs.mongodb.org/manual/administration/production-notes/#mongodb-on-numa-hardware&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/manual/administration/production-notes/#mongodb-on-numa-hardware&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;Thanks!&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                            <comment id="464593" author="kthummur" created="Tue, 3 Dec 2013 10:33:24 +0000"  >&lt;p&gt;Hi Mike,&lt;/p&gt;

&lt;p&gt;Please find my inputs for your queries &lt;br/&gt;
1. Current readahead configuration in machine&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;blockdev --getra /dev/mapper/VolGroup00-LogVol03&lt;br/&gt;
  256&lt;br/&gt;
  #&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;  If i understood correctly the current configuration of the readahead is set to 256 on setup even if the mongod uses 1K the rest of the 127K staying in system cache and it is not reverting back right?  To avoid the remainder will be in system cache i need to reduce the readahead from 256 to 32 ?&lt;/p&gt;

&lt;p&gt;2. Kernel version&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;cat /etc/redhat-release&lt;br/&gt;
  CentOS release 5.7 (Final)&lt;br/&gt;
  #&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;uname -r&lt;br/&gt;
  2.6.18-274.18.1.el5&lt;br/&gt;
  #&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;3. Hardware&lt;br/&gt;
  I am using UCS-B hardware and i created the virtual machine on top of the blades&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya &lt;/p&gt;
</comment>
                            <comment id="464134" author="michael.grundy@10gen.com" created="Mon, 2 Dec 2013 18:30:27 +0000"  >&lt;p&gt;Hi Krishnachaitanya -&lt;/p&gt;

&lt;p&gt;First, I meant to say 32 &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; If the volume is being shared by multiple databases, then tuning is a trade off between the different databases&apos; characteristics, and other programs accessing the volume. With the default (and I&apos;m guessing sda2 from the info you sent previously) of 256 and a block size of 512, each read will pull in 128K. If your document size is about 1K, then mongod will use the 1K, but the remainder will be in system cache. A readahead of 32 will only pull in 16K.&lt;/p&gt;

&lt;p&gt;Second, the swap numbers for mongod are concerning, more than from a &quot;general performance improvement that setting readahead properly will give&quot; point of view. Since the numbers you show from top in a previous comment don&apos;t show out of control mongod resident size, the swapped numer seems excessive.&lt;/p&gt;

&lt;p&gt;What Distro / Kernel version / Hardware are you running on ?&lt;/p&gt;

&lt;p&gt;Thanks!&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                            <comment id="464000" author="kthummur" created="Mon, 2 Dec 2013 16:28:37 +0000"  >&lt;p&gt;Hi Mike,&lt;/p&gt;

&lt;p&gt;After upgrade to 2.4.6 mongos process consumption of swap in between 316MB to 515MB and it&apos;s stayed there, and upgrade to 2.4.6 is helped for me.&lt;/p&gt;

&lt;p&gt;Thanks for your update, If i set the readahead value to 30, will it impact any other document which loads more than 30 in the same machine?&lt;br/&gt;
How can i calculate the readahead value based on the document size?&lt;/p&gt;

&lt;p&gt;Currently testing is in progress with mongo 2.4.6 and so for it&apos;s working fine. &lt;br/&gt;
To test your suggestions related to mongod swap consumption i can do after completion of the current testing only.&lt;/p&gt;

&lt;p&gt;As per your earlier comments if the fix for mongod swap consumption provide in the new build 2.4.7 then it&apos;s good. &lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya &lt;/p&gt;</comment>
                            <comment id="463918" author="michael.grundy@10gen.com" created="Mon, 2 Dec 2013 15:02:23 +0000"  >&lt;p&gt;Hi Krishnachaitanya -&lt;/p&gt;

&lt;p&gt;Did your mongos swap behavior stay reasonable after the upgrade? If you are still observing swap growth on mongos can you upload /proc/&amp;lt;pid&amp;gt;/smaps for the mongos process please?&lt;/p&gt;

&lt;p&gt;For your mongod memory consumption, you should drop your readahead to a lower value (blockdev --setra) on the volume containing your dbpath. 30 would probably be a more reasonable generic value, you can adjust it based on your document size to prevent loading unnecessary blocks into cache when reading in documents. &lt;/p&gt;

&lt;p&gt;Thanks!&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                            <comment id="432932" author="kthummur" created="Mon, 30 Sep 2013 05:53:46 +0000"  >&lt;p&gt;Any update ? &lt;br/&gt;
Could you please let me know.&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya&lt;/p&gt;</comment>
                            <comment id="431648" author="kthummur" created="Thu, 26 Sep 2013 06:38:25 +0000"  >&lt;p&gt;Hi Mike,&lt;/p&gt;

&lt;p&gt;Please find updated stat file attached.&lt;/p&gt;

&lt;p&gt;As you mentioned earlier 2.4.7 have fixes related to high memory usage of the mongod process, right now i am testing for the production 2.4.6 and i can&apos;t test the 2.4.7 before actual release. Will test 2.4.7 once i done testing with 2.4.6. &lt;/p&gt;

&lt;p&gt;Thanks for suggesting me and giving latest build.&lt;/p&gt;

&lt;p&gt;Without upgrade to 2.4.7 if you could give me any suggestion for reduce the swap memory usage of mongod process that would be helpful for me.&lt;/p&gt;

&lt;p&gt;Mongos process consumption:&lt;br/&gt;
I had provisioned the 4 Million documents to the DB for testing mongos process swap consumption, mongos process consumption of swap memory looks okay to me.&lt;/p&gt;

&lt;p&gt;After upgrade When i am testing the mongos process consumption of swap is increased from 316MB to 515MB and it&apos;s stayed there, it seems to upgrade to 2.4.6 is helped for me.&lt;/p&gt;

&lt;p&gt;FYI  &lt;br/&gt;
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  SWAP COMMAND&lt;br/&gt;
20287 root      15   0  542m  27m 3656 S  2.3  0.3  21:22.21 515m mongos&lt;br/&gt;
 4067 root      15   0  159m 6952 1360 S  0.0  0.1   2:21.19 152m snmpd&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya&lt;/p&gt;</comment>
                            <comment id="431647" author="kthummur" created="Thu, 26 Sep 2013 06:37:59 +0000"  >&lt;p&gt;Stats of the replica-sets&lt;/p&gt;</comment>
                            <comment id="431132" author="michael.grundy@10gen.com" created="Wed, 25 Sep 2013 15:22:19 +0000"  >&lt;p&gt;Could you also upload the contents of /proc/&amp;lt;pid&amp;gt;/stat (for the same mongod processes) and the output of free for each node?&lt;/p&gt;

&lt;p&gt;Thanks!&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                            <comment id="431112" author="kthummur" created="Wed, 25 Sep 2013 15:07:17 +0000"  >&lt;p&gt;System logs and mongostat logs&lt;/p&gt;</comment>
                            <comment id="431110" author="kthummur" created="Wed, 25 Sep 2013 15:06:19 +0000"  >&lt;p&gt;Hi Mike,&lt;/p&gt;

&lt;p&gt;Thanks for your inputs!&lt;/p&gt;

&lt;p&gt;Sorry for not to mentioned the mongod process issue earlier,  i mainly concentrated on the mongos process because I am using for provisioning due to this reason i did not mentioned it.&lt;/p&gt;

&lt;p&gt;largest mongod process is involved in the provisioning and same amount of swap is used by the all mongod process which is involved in provisioning, the smaller mongod process are different replica-set members which are in same nodes but involved in other tasks, I am interested on mongod process which is using more swap.&lt;/p&gt;

&lt;p&gt;Please find the attachment for logs which you are asking me.      &lt;br/&gt;
Logs are related to the mongod process which are using high swap.&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya&lt;/p&gt;</comment>
                            <comment id="431018" author="michael.grundy@10gen.com" created="Wed, 25 Sep 2013 13:21:21 +0000"  >&lt;p&gt;Hi Krishnachaitanya -&lt;/p&gt;

&lt;p&gt;First, as to your question about metadata upgrade, that only applies to a 2.2 -&amp;gt; 2.4 upgrade, not to a 2.4.x to 2.4.x&lt;/p&gt;

&lt;p&gt;You hadn&apos;t mentioned mongod having high swap, there are some fixes going into 2.4.7 that address high memory usage in mongod (and if you want to give it a test drive before it&apos;s released you can get it at &lt;a href=&quot;http://downloads.mongodb.org/linux/mongodb-linux-x86_64-v2.4-latest.tgz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://downloads.mongodb.org/linux/mongodb-linux-x86_64-v2.4-latest.tgz&lt;/a&gt;). &lt;/p&gt;

&lt;p&gt;That said, I would look to system configuration issues first. The information you posted shows ~94 gig of memory, but the largest mongod (are these all on the same machine, or sampled from different nodes?) is only 25g total and there is 65g free. &lt;/p&gt;

&lt;p&gt;Check the following:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;cat /proc/sys/vm/swappiness   (the default is 60)&lt;/li&gt;
	&lt;li&gt;run mongostat --all   , look at the mapped,  vsize, res, and  non-mapped values&lt;/li&gt;
	&lt;li&gt;run sudo blockdev --report , high readahead values affect mongod&apos;s ability to utilize as much memory as it could (read &lt;a href=&quot;http://www.kchodorow.com/blog/2012/05/10/thursday-5-diagnosing-high-readahead/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.kchodorow.com/blog/2012/05/10/thursday-5-diagnosing-high-readahead/&lt;/a&gt; )&lt;/li&gt;
	&lt;li&gt;post the output of all of these and /proc/&amp;lt;pid&amp;gt;/status where &amp;lt;pid&amp;gt; is the pid of the mongod process&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Thanks&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                            <comment id="430940" author="kthummur" created="Wed, 25 Sep 2013 07:05:15 +0000"  >&lt;p&gt;Hi &lt;/p&gt;

&lt;p&gt;After upgrade memory consumption of the mongod replica set member below.&lt;/p&gt;

&lt;p&gt;top - 00:41:14 up 1 day, 22:26,  1 user,  load average: 1.50, 3.21, 3.43&lt;br/&gt;
Tasks:  84 total,   1 running,  83 sleeping,   0 stopped,   0 zombie&lt;br/&gt;
Cpu(s):  0.8%us,  0.5%sy,  0.0%ni, 96.8%id,  1.2%wa,  0.0%hi,  0.7%si,  0.0%st&lt;br/&gt;
Mem:  99003004k total, 30394716k used, 68608288k free,  1630408k buffers&lt;br/&gt;
Swap:  6127608k total,        0k used,  6127608k free, 28167628k cached&lt;/p&gt;

&lt;p&gt;  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  SWAP COMMAND&lt;br/&gt;
31891 root      15   0 25.4g 758m 696m S  1.0  0.8   6:41.23  24g mongod&lt;br/&gt;
14426 root      15   0 6937m 2.9g 2.9g S  0.3  3.1   9:47.63 3.8g mongod&lt;br/&gt;
31679 root      15   0 3766m  61m  12m S  0.7  0.1  13:31.46 3.6g mongod&lt;br/&gt;
32024 root      15   0 3525m  75m  30m S  0.7  0.1   6:41.65 3.4g mongod&lt;br/&gt;
 4521 root      15   0  176m  29m 4360 S  0.0  0.0   0:32.35 146m snmpd&lt;/p&gt;

&lt;p&gt;In all members the mongod process swap memory consumption is same.&lt;/p&gt;

&lt;p&gt;The memory consumption of the mongos process is not yet tested, will let you know as early as possible&lt;/p&gt;

&lt;p&gt;I am not sure why mongod consuming more amount of the swap, could you please give me any suggestion?&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya  &lt;/p&gt;</comment>
                            <comment id="430937" author="kthummur" created="Wed, 25 Sep 2013 06:46:14 +0000"  >&lt;p&gt;Hi &lt;/p&gt;

&lt;p&gt;Upgraded a Replica Set from MongoDB 2.4.1 to MongoDB 2.4.6. &lt;/p&gt;

&lt;p&gt;Procedure to upgraded the shard cluster &quot;Meta-Data Upgrade Procedure&quot; steps mentioned in following link is required for 2.4.1 to 2.4.6?&lt;br/&gt;
&lt;a href=&quot;http://docs.mongodb.org/manual/release-notes/2.4-upgrade/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/manual/release-notes/2.4-upgrade/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Please suggest&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnahchaitanya &lt;/p&gt;</comment>
                            <comment id="430341" author="kthummur" created="Tue, 24 Sep 2013 13:52:48 +0000"  >&lt;p&gt;Thanks for your update!&lt;/p&gt;

&lt;p&gt;Will upgrade to 2.4.6 and will let you know&lt;/p&gt;

&lt;p&gt;Thanks &amp;amp; Regards&lt;br/&gt;
Krishnachaitanya&lt;/p&gt;</comment>
                            <comment id="430313" author="michael.grundy@10gen.com" created="Tue, 24 Sep 2013 13:17:36 +0000"  >&lt;p&gt;Upgrading to the latest version of MongoDB (currently 2.4.6) should resolve the memory leaks you are seeing. There are also several other important bug and stability fixes that have been included since 2.4.1, so I strongly recommend upgrading at your earliest convenience. As part of the 2.4 maintenance series, it should be a drop-in replacement. Please let us know when you have had a chance to upgrade and confirm that the upgrade fixes the issue you were seeing.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;br/&gt;
Mike&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="31814" name="Logs.rar" size="5159" author="kthummur" created="Wed, 25 Sep 2013 15:07:17 +0000"/>
                            <attachment id="31871" name="Replica_sets_stats.txt" size="3711" author="kthummur" created="Thu, 26 Sep 2013 06:37:59 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>19.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 24 Sep 2013 13:17:36 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        9 years, 45 weeks, 4 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>ramon.fernandez@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            9 years, 45 weeks, 4 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10026"><![CDATA[ALL]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>kthummur</customfieldvalue>
            <customfieldvalue>michael.grundy</customfieldvalue>
            <customfieldvalue>thomas.rueckstiess@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrmfl3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrt2j3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>83491</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_10750" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Steps To Reproduce</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p&gt;Provisioned 18 Million docs to database and each doc size around 1KB.&lt;/p&gt;

&lt;p&gt;After 3 to 4 hours i observed swap consumption of the mongos process reached maximum swap.&lt;/p&gt;</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|hrircv:</customfieldvalue>

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