<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:05:00 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-4118] mongos causes dos by opening a ton of connections</title>
                <link>https://jira.mongodb.org/browse/SERVER-4118</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Comment for future reference - this ticket was used primarily to track a writeback listener change in 2.0.1 - the wbl was not forcing a version reload which would reset the connection version on the mongod side, even after multiple failed retries.  The changes in this ticket fix that.  &lt;/p&gt;

&lt;p&gt;this issue may be similar to or related to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4037&quot; title=&quot;mongos: writeback failed because of stale config&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4037&quot;&gt;&lt;del&gt;SERVER-4037&lt;/del&gt;&lt;/a&gt;. previously, we have noted that mongos will enter a state in which it is attempting to retry a command query indefinitely to some shard members. prior to 2.0.0-rc2, this resulted in mongos outputting a bunch of &apos;writeback failed&apos; messages. this no longer occurs, but we still see behavior which cause the number of command ops/sec on shards to increase to 1500-2000 ops/sec range.  note, these command ops are not logged at the shards but we definitely see them when running mongostat.  bouncing mongos fixes the issue.&lt;/p&gt;

&lt;p&gt;on the shards, we can see that mongos effectively has caused a dos by issuing many quick successive connections:&lt;/p&gt;


&lt;p&gt;Fri Oct 21 11:50:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35539 #9663&lt;br/&gt;
Fri Oct 21 11:50:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35543 #9664&lt;br/&gt;
Fri Oct 21 11:50:51 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35544 #9665&lt;br/&gt;
Fri Oct 21 11:50:51 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35545 #9666&lt;br/&gt;
Fri Oct 21 11:50:53 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35546 #9667&lt;br/&gt;
Fri Oct 21 11:51:01 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35547 #9668&lt;br/&gt;
Fri Oct 21 11:51:02 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35551 #9669&lt;br/&gt;
Fri Oct 21 11:51:02 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35552 #9670&lt;br/&gt;
Fri Oct 21 11:51:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35553 #9671&lt;br/&gt;
Fri Oct 21 11:51:03 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35554 #9672&lt;br/&gt;
Fri Oct 21 11:51:05 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35558 #9673&lt;br/&gt;
Fri Oct 21 11:51:12 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35559 #9674&lt;br/&gt;
Fri Oct 21 11:51:13 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35560 #9675&lt;br/&gt;
Fri Oct 21 11:51:13 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35561 #9676&lt;br/&gt;
Fri Oct 21 11:51:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35565 #9677&lt;br/&gt;
Fri Oct 21 11:51:14 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35569 #9678&lt;br/&gt;
Fri Oct 21 11:51:16 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35570 #9679&lt;br/&gt;
Fri Oct 21 11:51:18 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35571 #9680&lt;br/&gt;
Fri Oct 21 11:51:18 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35572 #9681&lt;br/&gt;
Fri Oct 21 11:51:18 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35573 #9682&lt;br/&gt;
Fri Oct 21 11:51:19 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35577 #9683&lt;br/&gt;
Fri Oct 21 11:51:19 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35580 #9684&lt;br/&gt;
Fri Oct 21 11:51:19 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35581 #9685&lt;br/&gt;
Fri Oct 21 11:51:21 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35585 #9686&lt;br/&gt;
Fri Oct 21 11:51:22 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35586 #9687&lt;br/&gt;
Fri Oct 21 11:51:22 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35587 #9688&lt;br/&gt;
Fri Oct 21 11:51:29 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35591 #9689&lt;br/&gt;
Fri Oct 21 11:51:30 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35592 #9690&lt;br/&gt;
Fri Oct 21 11:51:31 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35593 #9691&lt;br/&gt;
Fri Oct 21 11:51:32 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35594 #9692&lt;br/&gt;
Fri Oct 21 11:51:34 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35595 #9693&lt;br/&gt;
Fri Oct 21 11:51:37 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35596 #9694&lt;br/&gt;
Fri Oct 21 11:51:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35597 #9695&lt;br/&gt;
Fri Oct 21 11:51:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35598 #9696&lt;br/&gt;
Fri Oct 21 11:51:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35599 #9697&lt;br/&gt;
Fri Oct 21 11:51:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35600 #9698&lt;br/&gt;
Fri Oct 21 11:51:41 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35601 #9699&lt;br/&gt;
Fri Oct 21 11:51:42 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35602 #9700&lt;br/&gt;
Fri Oct 21 11:51:42 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35603 #9701&lt;br/&gt;
Fri Oct 21 11:51:42 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35604 #9702&lt;br/&gt;
Fri Oct 21 11:51:43 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35605 #9703&lt;br/&gt;
Fri Oct 21 11:51:44 &lt;span class=&quot;error&quot;&gt;&amp;#91;initandlisten&amp;#93;&lt;/span&gt; connection accepted from mongos:35609 #9704&lt;br/&gt;
...&lt;/p&gt;


&lt;p&gt;the load on this shard RS member increased to 15 and became unresponsive.  bouncing mongos stopped the connections/queries and service returned to normal. during the initial stages of the problem, performance degraded severely eventually leading to all queries timing out.&lt;/p&gt;</description>
                <environment>ubuntu 10.04 x86_64; 4 shards, each shard a RS of two members + arbiter</environment>
        <key id="23924">SERVER-4118</key>
            <summary>mongos causes dos by opening a ton of connections</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="greg_10gen">Greg Studer</assignee>
                                    <reporter username="wayne530">Y. Wayne Huang</reporter>
                        <labels>
                            <label>mongos</label>
                    </labels>
                <created>Fri, 21 Oct 2011 19:25:54 +0000</created>
                <updated>Mon, 11 Jul 2016 18:33:56 +0000</updated>
                            <resolved>Thu, 8 Dec 2011 17:50:58 +0000</resolved>
                                    <version>2.0.0-rc2</version>
                                    <fixVersion>2.0.2</fixVersion>
                                    <component>Performance</component>
                    <component>Sharding</component>
                    <component>Stability</component>
                                        <votes>2</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="71742" author="greg_10gen" created="Thu, 8 Dec 2011 17:50:38 +0000"  >&lt;p&gt;np - definitely let us know if you see this again or any other issue.  Closing for now - feel free to reopen if you see this issue again.  &lt;/p&gt;</comment>
                            <comment id="71736" author="wayne530" created="Thu, 8 Dec 2011 17:40:47 +0000"  >&lt;p&gt;we&apos;re running 2.0.2 rc1 for mongos and 2.0.1 for mongod and so far so good. thanks for the fix&lt;/p&gt;</comment>
                            <comment id="66058" author="greg_10gen" created="Thu, 10 Nov 2011 23:54:54 +0000"  >&lt;p&gt;Should be within a week for rc0.  Just pushed some backwards-compatibility changes as well.  &lt;/p&gt;</comment>
                            <comment id="65760" author="greg_10gen" created="Wed, 9 Nov 2011 21:20:36 +0000"  >&lt;p&gt;Not exactly sure, having a scheduling meeting tomorrow, so will update.  We need to do more testing of the final branch once we freeze it too.&lt;/p&gt;</comment>
                            <comment id="65756" author="wayne530" created="Wed, 9 Nov 2011 20:52:54 +0000"  >&lt;p&gt;when can we expect 2.0.2?&lt;/p&gt;</comment>
                            <comment id="65755" author="greg_10gen" created="Wed, 9 Nov 2011 20:47:33 +0000"  >&lt;p&gt;&amp;gt; Wed Nov 9 12:24:42 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn7&amp;#93;&lt;/span&gt; warning: adding shard sub-connection shard1/a:27011,b:27012 (parent shard1/a:27011,b:27012) as sharded, this is safe but unexpected&lt;br/&gt;
This is safe, just too-verbose conn tracking messaging, been removed in 2.0.2.  It should only occur more than once at high verbosity levels.&lt;/p&gt;

&lt;p&gt;&amp;gt; could not initialize cursor across all shards because : could not initialize sharding on connection shard3/x:27017,y:27017 :: caused by :: need to specify namespace&lt;br/&gt;
Apologize for this - the new connection initialization in the new nightly requires new mongod as well, as the protocol has slightly changed.  Will make sure this is more seamless for the release. &lt;/p&gt;
</comment>
                            <comment id="65752" author="wayne530" created="Wed, 9 Nov 2011 20:30:19 +0000"  >&lt;p&gt;also see this in the mongos log:&lt;/p&gt;


&lt;p&gt;Wed Nov  9 12:24:42 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn7&amp;#93;&lt;/span&gt; warning: adding shard sub-connection shard1/a:27011,b:27012 (parent shard1/a:27011,b:27012) as sharded, this is safe but unexpected&lt;br/&gt;
0x5c5fe1 0x5c37d5 0x5c3c5c 0x7967ae 0x796e5e 0x79088f 0x76a6bb 0x7b1627 0x7c37c1 0x5e9557 0x7fe99da279ca 0x7fe99cfd670d &lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo17ClientConnections3getERKSsS2_b+0x571) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x5c5fe1&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo15ShardConnection5_initEb+0x65) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x5c37d5&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo15ShardConnectionC1ERKNS_5ShardERKSsb+0x8c) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x5c3c5c&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo15dbgrid_pub_cmds17PublicGridCommand12_passthroughERKSsN5boost10shared_ptrINS_8DBConfigEEERKNS_7BSONObjEiRNS_14BSONObjBuilderE+0x15e) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7967ae&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo15dbgrid_pub_cmds32NotAllowedOnShardedCollectionCmd3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x13e) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x796e5e&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo7Command20runAgainstRegisteredEPKcRNS_7BSONObjERNS_14BSONObjBuilderEi+0x89f) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x79088f&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo14SingleStrategy7queryOpERNS_7RequestE+0x5cb) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x76a6bb&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo7Request7processEi+0x187) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7b1627&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo21ShardedMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x71) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7c37c1&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /usr/bin/mongos(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x287) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x5e9557&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /lib/libpthread.so.0(+0x69ca) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7fe99da279ca&amp;#93;&lt;/span&gt;&lt;br/&gt;
 /lib/libc.so.6(clone+0x6d) &lt;span class=&quot;error&quot;&gt;&amp;#91;0x7fe99cfd670d&amp;#93;&lt;/span&gt;&lt;/p&gt;</comment>
                            <comment id="65750" author="wayne530" created="Wed, 9 Nov 2011 20:27:12 +0000"  >&lt;p&gt;not sure if it&apos;s another fix in head but the 2.0.1 nightly build for 11/9 caused our entire site to go down. all queries returned the following error:&lt;br/&gt;
could not initialize cursor across all shards because : could not initialize sharding on connection shard3/x:27017,y:27017 :: caused by :: need to specify namespace&lt;/p&gt;

&lt;p&gt;we&apos;ve rolled back to 2.0.1 stable.&lt;/p&gt;</comment>
                            <comment id="65599" author="greg_10gen" created="Wed, 9 Nov 2011 01:45:52 +0000"  >&lt;p&gt;Just mongos.&lt;/p&gt;</comment>
                            <comment id="65506" author="wayne530" created="Tue, 8 Nov 2011 19:58:45 +0000"  >&lt;p&gt;should we update just mongos or do we need to update mongod as well?&lt;/p&gt;</comment>
                            <comment id="65497" author="greg_10gen" created="Tue, 8 Nov 2011 19:25:24 +0000"  >&lt;p&gt;The writebacklistener fix has been backported, in the 2.0.1 nightly now (staged for 2.0.2), if you&apos;d like to try it.  &lt;/p&gt;</comment>
                            <comment id="65452" author="wayne530" created="Tue, 8 Nov 2011 16:20:43 +0000"  >&lt;p&gt;any updates?&lt;/p&gt;</comment>
                            <comment id="64187" author="greg_10gen" created="Wed, 2 Nov 2011 14:03:37 +0000"  >&lt;p&gt;will post once a build with this patch is available.  &lt;/p&gt;</comment>
                            <comment id="64070" author="auto" created="Tue, 1 Nov 2011 22:52:50 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;gregstuder&apos;, u&apos;name&apos;: u&apos;gregs&apos;, u&apos;email&apos;: u&apos;greg@10gen.com&apos;}
&lt;p&gt;Message: force reload of config after two failed wbl checks &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4118&quot; title=&quot;mongos causes dos by opening a ton of connections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4118&quot;&gt;&lt;del&gt;SERVER-4118&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: v2.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/bcf4ca44072d45f4e8d87a3341350596ef54bff2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/bcf4ca44072d45f4e8d87a3341350596ef54bff2&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="64069" author="auto" created="Tue, 1 Nov 2011 22:52:44 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;gregstuder&apos;, u&apos;name&apos;: u&apos;gregs&apos;, u&apos;email&apos;: u&apos;greg@10gen.com&apos;}
&lt;p&gt;Message: force reload of config after two failed wbl checks &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4118&quot; title=&quot;mongos causes dos by opening a ton of connections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4118&quot;&gt;&lt;del&gt;SERVER-4118&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: v2.0&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/bcf4ca44072d45f4e8d87a3341350596ef54bff2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/bcf4ca44072d45f4e8d87a3341350596ef54bff2&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="64068" author="auto" created="Tue, 1 Nov 2011 22:49:46 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;gregstuder&apos;, u&apos;name&apos;: u&apos;gregs&apos;, u&apos;email&apos;: u&apos;greg@10gen.com&apos;}
&lt;p&gt;Message: force reload of config after two failed wbl checks &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4118&quot; title=&quot;mongos causes dos by opening a ton of connections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4118&quot;&gt;&lt;del&gt;SERVER-4118&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/c96569dc11ed389c7ea279d52b65753aa9946b18&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/c96569dc11ed389c7ea279d52b65753aa9946b18&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="64067" author="auto" created="Tue, 1 Nov 2011 22:49:40 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;login&apos;: u&apos;gregstuder&apos;, u&apos;name&apos;: u&apos;gregs&apos;, u&apos;email&apos;: u&apos;greg@10gen.com&apos;}
&lt;p&gt;Message: force reload of config after two failed wbl checks &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4118&quot; title=&quot;mongos causes dos by opening a ton of connections&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4118&quot;&gt;&lt;del&gt;SERVER-4118&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/c96569dc11ed389c7ea279d52b65753aa9946b18&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/c96569dc11ed389c7ea279d52b65753aa9946b18&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="64064" author="greg_10gen" created="Tue, 1 Nov 2011 22:28:51 +0000"  >&lt;p&gt;From the logs, this now seems like a related but different issue - shard version isn&apos;t getting force-reloaded after multiple retries.&lt;/p&gt;</comment>
                            <comment id="64046" author="wayne530" created="Tue, 1 Nov 2011 21:12:26 +0000"  >&lt;p&gt;any updates? we see this behavior affect our cluster about 2-3 times per week and a google search seems to reveal others are seeing it as well&lt;/p&gt;</comment>
                            <comment id="63275" author="wayne530" created="Fri, 28 Oct 2011 06:42:00 +0000"  >&lt;p&gt;log file for today attached&lt;/p&gt;</comment>
                            <comment id="63274" author="wayne530" created="Fri, 28 Oct 2011 06:17:36 +0000"  >&lt;p&gt;{&lt;br/&gt;
	&quot;host&quot; : &quot;mongos-1&quot;,&lt;br/&gt;
	&quot;version&quot; : &quot;2.0.1&quot;,&lt;br/&gt;
	&quot;process&quot; : &quot;mongos&quot;,&lt;br/&gt;
	&quot;uptime&quot; : 19326,&lt;br/&gt;
	&quot;localTime&quot; : ISODate(&quot;2011-10-28T06:11:30.833Z&quot;),&lt;br/&gt;
	&quot;mem&quot; : &lt;/p&gt;
{
		&quot;resident&quot; : 14,
		&quot;virtual&quot; : 245,
		&quot;supported&quot; : true
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;connections&quot; : &lt;/p&gt;
{
		&quot;current&quot; : 9,
		&quot;available&quot; : 15991
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;extra_info&quot; : &lt;/p&gt;
{
		&quot;note&quot; : &quot;fields vary by platform&quot;,
		&quot;heap_usage_bytes&quot; : 952000,
		&quot;page_faults&quot; : 0
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;opcounters&quot; : &lt;/p&gt;
{
		&quot;insert&quot; : 123760,
		&quot;query&quot; : 49708,
		&quot;update&quot; : 149348,
		&quot;delete&quot; : 4,
		&quot;getmore&quot; : 5575,
		&quot;command&quot; : 109302
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;ops&quot; : {&lt;br/&gt;
		&quot;sharded&quot; : &lt;/p&gt;
{
			&quot;insert&quot; : 52682,
			&quot;query&quot; : 9022,
			&quot;update&quot; : 86423,
			&quot;delete&quot; : 4,
			&quot;getmore&quot; : 5360,
			&quot;command&quot; : 0
		}
&lt;p&gt;,&lt;br/&gt;
		&quot;notSharded&quot; : &lt;/p&gt;
{
			&quot;insert&quot; : 71078,
			&quot;query&quot; : 40686,
			&quot;update&quot; : 62925,
			&quot;delete&quot; : 0,
			&quot;getmore&quot; : 215,
			&quot;command&quot; : 109302
		}
&lt;p&gt;	},&lt;br/&gt;
	&quot;shardCursorType&quot; : &lt;/p&gt;
{
		&quot;ParallelSort&quot; : 9022
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;asserts&quot; : &lt;/p&gt;
{
		&quot;regular&quot; : 0,
		&quot;warning&quot; : 0,
		&quot;msg&quot; : 0,
		&quot;user&quot; : 721,
		&quot;rollovers&quot; : 0
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;network&quot; : &lt;/p&gt;
{
		&quot;bytesIn&quot; : 403446802,
		&quot;bytesOut&quot; : 3332333902,
		&quot;numRequests&quot; : 341639
	}
&lt;p&gt;,&lt;br/&gt;
	&quot;ok&quot; : 1&lt;br/&gt;
}&lt;/p&gt;</comment>
                            <comment id="63273" author="eliot" created="Fri, 28 Oct 2011 06:09:54 +0000"  >&lt;p&gt;Can you send db.serverStatus() and the full mongos log?&lt;/p&gt;</comment>
                            <comment id="63272" author="wayne530" created="Fri, 28 Oct 2011 06:07:32 +0000"  >&lt;p&gt;we&apos;ve since upgraded to 2.0.1 (from your repo) and still see the issue.&lt;/p&gt;</comment>
                            <comment id="63270" author="eliot" created="Fri, 28 Oct 2011 06:02:38 +0000"  >&lt;p&gt;Are you still on 2.0.0-rc2?&lt;br/&gt;
There was a change for 2.0.1 that might be an issue.&lt;/p&gt;</comment>
                            <comment id="63269" author="wayne530" created="Fri, 28 Oct 2011 06:00:58 +0000"  >&lt;p&gt;any updates?&lt;/p&gt;</comment>
                            <comment id="62535" author="wayne530" created="Tue, 25 Oct 2011 16:49:07 +0000"  >&lt;p&gt;that mongostat was hard to read.. this might be better:&lt;br/&gt;
&lt;a href=&quot;https://skitch.com/wayne530/gdce6/mongostat&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://skitch.com/wayne530/gdce6/mongostat&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="62533" author="wayne530" created="Tue, 25 Oct 2011 16:46:55 +0000"  >&lt;p&gt;Greg, we are seeing the same issue right now. mongos appears to be retrying some type of query infinitely, resulting in a &apos;shard version not ok in Client::Context&apos; each time:&lt;/p&gt;


&lt;p&gt;Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1886&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;br/&gt;
Tue Oct 25 09:39:50 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn1880&amp;#93;&lt;/span&gt; Assertion: 13388:&lt;span class=&quot;error&quot;&gt;&amp;#91;mydb.mycoll&amp;#93;&lt;/span&gt; shard version not ok in Client::Context: client in sharded mode, but doesn&apos;t have version set for this collection: mydb.mycoll myVersion: 155|3&lt;/p&gt;

&lt;p&gt;here is mongostat from the affected shard:&lt;/p&gt;


&lt;p&gt;insert  query update delete getmore command flushes mapped  vsize    res faults locked % idx miss %     qr|qw   ar|aw  netIn netOut  conn    set repl       time &lt;br/&gt;
     4      0      0      0       4    2562       0   132g   265g  3.12g      1     15.9          0       0|0     1|1   431k   569k    87 shard2    M   09:44:26 &lt;br/&gt;
     0      0      0      0       0    2341       0   132g   265g  3.12g      0     12.5          0       0|0     1|1   393k   516k    87 shard2    M   09:44:27 &lt;br/&gt;
     1      0      0      0       1    2546       0   132g   265g  3.12g      4     18.3          0       0|0     1|1   429k   562k    87 shard2    M   09:44:28 &lt;br/&gt;
     1      0      0      0       1    2620       0   132g   265g  3.12g      0     14.7          0       0|0     1|1   442k   582k    87 shard2    M   09:44:29 &lt;br/&gt;
     1      0      0      0       1    2562       0   132g   265g  3.12g      0     14.4          0       0|0     1|1   433k   570k    87 shard2    M   09:44:30 &lt;br/&gt;
     7      0      0      0       7    2490       0   132g   265g  3.12g      1     17.1          0       0|0     1|1   421k   556k    87 shard2    M   09:44:31 &lt;br/&gt;
     0      0      0      0       0    2531       0   132g   265g  3.12g      0     14.1          0       0|0     2|1   425k   557k    87 shard2    M   09:44:32 &lt;br/&gt;
     8      0      0      0       4    2592       0   132g   265g  3.12g      0     15.6          0       0|0     1|1   436k   575k    87 shard2    M   09:44:33 &lt;br/&gt;
     0      0      0      0       0    2374       0   132g   265g  3.12g      0       14          0       0|0     1|1   397k   521k    87 shard2    M   09:44:34 &lt;br/&gt;
     1      0      0      0       1    2456       0   132g   265g  3.12g      0     14.4          0       0|0     2|1   414k   543k    87 shard2    M   09:44:35 &lt;br/&gt;
insert  query update delete getmore command flushes mapped  vsize    res faults locked % idx miss %     qr|qw   ar|aw  netIn netOut  conn    set repl       time &lt;br/&gt;
     0      0      0      0       0    2585       0   132g   265g  3.11g      0     14.9          0       0|0     2|1   434k   574k    87 shard2    M   09:44:36 &lt;br/&gt;
     1      0      0      0       1    2194       0   132g   265g  3.11g      0     12.3          0       0|0     1|1   368k   483k    87 shard2    M   09:44:37 &lt;br/&gt;
     2      0      0      0       2    2545       0   132g   265g  3.11g      0     14.4          0       0|0     1|1   436k   575k    87 shard2    M   09:44:38 &lt;br/&gt;
     0      0      0      0       0    2514       0   132g   265g  3.11g      0     13.4          0       3|1     3|1   419k   551k    87 shard2    M   09:44:39 &lt;br/&gt;
     1      0      0      0       1    2657       0   132g   265g  3.11g      0     14.2          0       0|0     1|1   446k   585k    87 shard2    M   09:44:40 &lt;br/&gt;
     3      0      0      0       3    2558       0   132g   265g  3.11g      0     16.6          0       0|0     1|1   432k   571k    87 shard2    M   09:44:41 &lt;br/&gt;
     0      0      0      0       0    2444       0   132g   265g  3.11g      0       14          0       0|0     1|1   410k   538k    87 shard2    M   09:44:42 &lt;br/&gt;
    10      0      0      0       8    2684       0   132g   265g  3.11g      0     13.8          0       0|0     1|1   454k   599k    87 shard2    M   09:44:43 &lt;br/&gt;
     4      0      0      0       4    2546       0   132g   265g  3.11g      0       14          0       0|0     1|1   429k   562k    87 shard2    M   09:44:44 &lt;br/&gt;
     1      0      0      0       1    2464       0   132g   265g  3.11g      0     13.4          0       0|0     1|1   415k   545k    87 shard2    M   09:44:45 &lt;br/&gt;
insert  query update delete getmore command flushes mapped  vsize    res faults locked % idx miss %     qr|qw   ar|aw  netIn netOut  conn    set repl       time &lt;br/&gt;
     1      0      0      0       1    2483       0   132g   265g  3.11g      1     13.9          0       0|0     1|1   420k   555k    87 shard2    M   09:44:46 &lt;br/&gt;
     1      0      0      0       1    2447       0   132g   265g  3.11g      0     12.8          0       0|0     1|1   411k   540k    87 shard2    M   09:44:47 &lt;br/&gt;
     0      0      0      0       0    2404       0   132g   265g  3.11g      0     12.2          0       0|0     2|1   402k   527k    87 shard2    M   09:44:48 &lt;br/&gt;
     0      0      0      0       0     115       0   132g   265g  3.11g      0      0.5          0       0|0     1|1    18k    28k    57 shard2    M   09:44:49 &lt;br/&gt;
     0      0      0      0       1       2       0   132g   265g  3.11g      0        0          0       0|0     1|1   241b     1k    57 shard2    M   09:44:50 &lt;br/&gt;
     0      0      0      0       0       8       0   132g   265g  3.11g      0        0          0       0|0     1|1   566b     4k    57 shard2    M   09:44:51 &lt;br/&gt;
     0      0      0      0       1       2       0   132g   265g  3.11g      0        0          0       0|0     1|1   241b     1k    57 shard2    M   09:44:52 &lt;br/&gt;
     0      0      0      0       0      14       0   132g   265g  3.11g      0        0          0       0|0     1|1   938b     7k    57 shard2    M   09:44:53 &lt;br/&gt;
     6      0      0      0       3       6       0   132g   265g   3.1g      0      0.2          0       0|0     1|1     2k     4k    45 shard2    M   09:44:54 &lt;br/&gt;
     0      0      0      0       0       8       0   132g   265g   3.1g      0        0          0       0|0     1|1   726b     2k    48 shard2    M   09:44:55 &lt;br/&gt;
insert  query update delete getmore command flushes mapped  vsize    res faults locked % idx miss %     qr|qw   ar|aw  netIn netOut  conn    set repl       time &lt;br/&gt;
     0      0      0      0       1      16       0   132g   265g   3.1g      0        0          0       0|0     1|1     1k     7k    49 shard2    M   09:44:56 &lt;br/&gt;
     1      0      0      0       1       5       0   132g   265g   3.1g      0        0          0       0|0     1|1     1k     2k    49 shard2    M   09:44:57 &lt;br/&gt;
     1      0      0      0       1       4       0   132g   265g   3.1g     32        0          0       0|0     2|1   894b     2k    49 shard2    M   09:44:58 &lt;/p&gt;


&lt;p&gt;i&apos;m sure you can guess when i bounced mongos.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://skitch.com/wayne530/gdc89/mongodb-ops&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://skitch.com/wayne530/gdc89/mongodb-ops&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;i don&apos;t think this is some kind of transient system issue as it&apos;s pretty clear that mongos is retrying some type of command query repeatedly.&lt;/p&gt;</comment>
                            <comment id="62280" author="greg_10gen" created="Mon, 24 Oct 2011 18:18:04 +0000"  >&lt;p&gt;As a workaround - you can set the maxConns parameter in mongos &amp;gt;= 1.8.3 to limit the maximum number of connections it will open per-host - the default behavior is to try to service requests no matter how fast they come in.  &lt;/p&gt;

&lt;p&gt;Also, if you increase the verbosity of mongos and mongod to logLevel : 2 - do you see the commands being (re)-sent?  &lt;/p&gt;

&lt;p&gt;This may be a systemic issue - where a small backup on the primary causes new connections and larger backups on the primary, and so on...&lt;/p&gt;

</comment>
                            <comment id="61890" author="wayne530" created="Fri, 21 Oct 2011 20:34:17 +0000"  >&lt;p&gt;shard2 command ops graph:&lt;br/&gt;
&lt;a href=&quot;https://skitch.com/wayne530/gnwc4/shard2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://skitch.com/wayne530/gnwc4/shard2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;unfortunately, during this process, with mongos (v2.0.1-pre-  git:a7a36ecbf060624a1bfcf36e0a00de02b907c019) there is no log output. the affected shard primaries also do not log the command queries being performed, however we definitely see them show up in the count using mongostat. &lt;/p&gt;</comment>
                            <comment id="61886" author="wayne530" created="Fri, 21 Oct 2011 20:28:20 +0000"  >&lt;p&gt;upon further investigation, the log messages above may be unrelated.  here&apos;s what we see:&lt;/p&gt;

&lt;p&gt;command ops/sec on some shard primaries will increase to 1500-2000 ops/sec, during which performance is degraded. bouncing mongos fixes the issue. it appears that asking an affected primary to stepdown stops the activity momentarily but eventually the problem will also affect the new primary. it seems bouncing mongos is the only sure way to stop the issue for an extended period of time.&lt;/p&gt;

&lt;p&gt;the above issue we believe is different. there&apos;s an rsSync process running which has a global write lock. to the best of my knowledge, it&apos;s supposed to yield that lock as necessary. what we saw occur is that the process stopped yielding the lock, thus causing commands to pile up behind it. the connections from mongos, normally short-lived, now persist because the command it is routing is blocking due to the apparently non-yielding global write lock from the rsSync process. the above connections are within range for our typical workload (~10-20 ops/sec).  when viewing db.currentOp() during the pile up, the only process with a write lock was this rsSync process:&lt;/p&gt;


&lt;p&gt;		{&lt;br/&gt;
			&quot;opid&quot; : &quot;shard1:23606014&quot;,&lt;br/&gt;
			&quot;active&quot; : true,&lt;br/&gt;
			&quot;lockType&quot; : &quot;write&quot;,&lt;br/&gt;
			&quot;waitingForLock&quot; : false,&lt;br/&gt;
			&quot;secs_running&quot; : 5497,&lt;br/&gt;
			&quot;op&quot; : &quot;none&quot;,&lt;br/&gt;
			&quot;ns&quot; : &quot;mydb.mycoll&quot;,&lt;br/&gt;
			&quot;query&quot; : {&lt;/p&gt;

&lt;p&gt;			},&lt;br/&gt;
			&quot;client_s&quot; : &quot;&quot;,&lt;br/&gt;
			&quot;desc&quot; : &quot;rsSync&quot;,&lt;br/&gt;
			&quot;threadId&quot; : &quot;0x7fec5b5f8700&quot;,&lt;br/&gt;
			&quot;numYields&quot; : 1&lt;br/&gt;
		},&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="24707">SERVER-4240</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="21480">SERVER-3683</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="13637" name="mongodb.scrubbed.log.gz" size="26018763" author="wayne530" created="Fri, 28 Oct 2011 06:41:42 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>30.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 24 Oct 2011 18:18:04 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        12 years, 10 weeks, 6 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<s><a href='https://jira.mongodb.org/browse/SERVER-4240'>SERVER-4240</a></s>]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_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>
                            12 years, 10 weeks, 6 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="10020"><![CDATA[Linux]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>auto</customfieldvalue>
            <customfieldvalue>eliot</customfieldvalue>
            <customfieldvalue>greg_10gen</customfieldvalue>
            <customfieldvalue>wayne530</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hronlb:</customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>22982</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|hs91yf:</customfieldvalue>

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