<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:11:17 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-6297] Socket Exception code 9001</title>
                <link>https://jira.mongodb.org/browse/SERVER-6297</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Hi.&lt;/p&gt;

&lt;p&gt;I have a sharded cluster using authentication.  If I stop one of the config servers along with one of my data nodes, I start getting this error when attempting to connect to mongos and run any commands: uncaught exception: error &lt;/p&gt;
{ &quot;$err&quot; : &quot;socket exception&quot;, &quot;code&quot; : 9001 }
&lt;p&gt;.&lt;/p&gt;

&lt;p&gt;The problem appears to be worse in 2.0.6.  If I just shut down a single config server in 2.0.6 I immediately start getting socket exception errors.&lt;/p&gt;

&lt;p&gt;Looks like this is probably related to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-6178&quot; title=&quot;Cannot use mongos if subset of config servers can&amp;#39;t read from or write to disk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-6178&quot;&gt;&lt;del&gt;SERVER-6178&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Steps to reproduce:&lt;/p&gt;

&lt;p&gt;1. Create a sharded authenticated database with the following config&lt;/p&gt;

&lt;p&gt;2 shards - 2xdata, 1xarb&lt;br/&gt;
3 config dbs&lt;br/&gt;
1 mongos&lt;/p&gt;

&lt;p&gt;2. Add an admin user&lt;/p&gt;

&lt;p&gt;3. Stop one configdb&lt;/p&gt;

&lt;p&gt;4. Stop secondary on one shard&lt;/p&gt;

&lt;p&gt;5. Wait a few minutes - seems to start after syncluster fails&lt;/p&gt;

&lt;p&gt;6. Attempt to connect&lt;/p&gt;

&lt;p&gt;I turned up logging in mongos and got the following:&lt;/p&gt;

&lt;p&gt;Tue Jul  3 22:04:33 &lt;span class=&quot;error&quot;&gt;&amp;#91;mongosMain&amp;#93;&lt;/span&gt; connection accepted from 127.0.0.1:62779 #32&lt;br/&gt;
Tue Jul  3 22:04:33 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn32&amp;#93;&lt;/span&gt;  authenticate: &lt;/p&gt;
{ authenticate: 1.0, user: &quot;admin&quot;, nonce: &quot;ee41c70123ef341&quot;, key: &quot;dc29f18bef6f52f3abf09f0f49574f83&quot; }
&lt;p&gt;Tue Jul  3 22:04:33 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn32&amp;#93;&lt;/span&gt; DBClientCursor::init call() failed&lt;br/&gt;
Tue Jul  3 22:04:33 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn32&amp;#93;&lt;/span&gt; sharded connection to localhost:50010,localhost:50020,localhost:50030 not being returned to the pool&lt;br/&gt;
Tue Jul  3 22:04:33 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn32&amp;#93;&lt;/span&gt; end connection 127.0.0.1:62779&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;ReplicaSetMonitorWatcher&amp;#93;&lt;/span&gt; trying reconnect to localhost:20020&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;ReplicaSetMonitorWatcher&amp;#93;&lt;/span&gt; reconnect localhost:20020 failed couldn&apos;t connect to server localhost:20020&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50010&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50020&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50030&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; SyncClusterConnection connect fail to: localhost:50030 errmsg: couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; trying reconnect to localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; reconnect localhost:50030 failed couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:35 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; warning: distributed lock pinger &apos;localhost:50010,localhost:50020,localhost:50030/Jeffs-MacBook-Air.local:27017:1341378125:16807&apos; detected an exception while pinging. :: caused by :: socket exception&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;mongosMain&amp;#93;&lt;/span&gt; connection accepted from 127.0.0.1:62792 #33&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt;  authenticate: &lt;/p&gt;
{ authenticate: 1.0, user: &quot;admin&quot;, nonce: &quot;320e3c628074ca23&quot;, key: &quot;9e5c499327208a089c7cdab6e16bd5dc&quot; }
&lt;p&gt;Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50010&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50020&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50030&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; SyncClusterConnection connect fail to: localhost:50030 errmsg: couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; trying reconnect to localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; reconnect localhost:50030 failed couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; DBException in process: socket exception&lt;br/&gt;
Tue Jul  3 22:04:38 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn33&amp;#93;&lt;/span&gt; end connection 127.0.0.1:62792&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;mongosMain&amp;#93;&lt;/span&gt; connection accepted from 127.0.0.1:62800 #34&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt;  authenticate: &lt;/p&gt;
{ authenticate: 1.0, user: &quot;admin&quot;, nonce: &quot;6d642df666f58f77&quot;, key: &quot;058a8a22d7a7d96b486bdce134e53026&quot; }
&lt;p&gt;Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50010&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50020&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;localhost:50030&amp;#93;&lt;/span&gt;&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; SyncClusterConnection connect fail to: localhost:50030 errmsg: couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; trying reconnect to localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; reconnect localhost:50030 failed couldn&apos;t connect to server localhost:50030&lt;br/&gt;
Tue Jul  3 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; DBException in process: socket exception&lt;br/&gt;
Tue Jul  4 22:04:40 &lt;span class=&quot;error&quot;&gt;&amp;#91;conn34&amp;#93;&lt;/span&gt; end connection 127.0.0.1:62800&lt;/p&gt;</description>
                <environment>OSX, linux</environment>
        <key id="43334">SERVER-6297</key>
            <summary>Socket Exception code 9001</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="3">Duplicate</resolution>
                                        <assignee username="greg_10gen">Greg Studer</assignee>
                                    <reporter username="jlee">Jeff lee</reporter>
                        <labels>
                            <label>authentication</label>
                            <label>configserver</label>
                            <label>mongos</label>
                    </labels>
                <created>Wed, 4 Jul 2012 06:22:28 +0000</created>
                <updated>Wed, 15 Aug 2012 14:04:11 +0000</updated>
                            <resolved>Tue, 10 Jul 2012 17:19:22 +0000</resolved>
                                    <version>2.0.4</version>
                    <version>2.0.6</version>
                                                    <component>Security</component>
                    <component>Sharding</component>
                                        <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="141411" author="greg_10gen" created="Tue, 10 Jul 2012 17:19:48 +0000"  >&lt;p&gt;Resolved as duplicate for better triaging.  &lt;/p&gt;</comment>
                            <comment id="140988" author="greg_10gen" created="Mon, 9 Jul 2012 19:31:45 +0000"  >&lt;p&gt;Thanks for the log - think I see the issue.  Sort-of related to time, think this happens when the connection pool to the config server becomes empty after successive errors, and needs to be re-authed.  &lt;/p&gt;</comment>
                            <comment id="140510" author="jlee" created="Fri, 6 Jul 2012 21:48:19 +0000"  >&lt;p&gt;Narrowed it down a bit.  Seems like things go south as soon as I get this in the mongos log:&lt;/p&gt;

&lt;p&gt;Fri Jul  6 14:45:49 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; warning: distributed lock pinger &apos;localhost:50010,localhost:50020,localhost:50030/Jeffs-MacBook-Air.local:27017:1341611119:16807&apos; detected an exception while pinging. :: caused by :: SyncClusterConnection::udpate prepare failed: 10276 DBClientBase::findN: transport error: localhost:50030 query: &lt;/p&gt;
{ fsync: 1 }
&lt;p&gt; localhost:50030:{}&lt;/p&gt;

&lt;p&gt;$ mongo localhost/admin -u admin -p admin&lt;br/&gt;
MongoDB shell version: 2.0.6&lt;br/&gt;
connecting to: localhost/admin&lt;br/&gt;
Fri Jul  6 14:45:50 uncaught exception: error &lt;/p&gt;
{ &quot;$err&quot; : &quot;socket exception&quot;, &quot;code&quot; : 9001 }
&lt;p&gt;exception: login failed&lt;/p&gt;</comment>
                            <comment id="140499" author="jlee" created="Fri, 6 Jul 2012 21:26:39 +0000"  >&lt;p&gt;Sure thing - here ya go.  &lt;/p&gt;

&lt;p&gt;I restarted mongos after creating the admin user.  Here&apos;s the log after starting it back up with -vvvvv.  You may need to wait a bit for the socket exception to occur it seems to be after the synccluster fails.&lt;/p&gt;

&lt;p&gt;It&apos;s at line 337 here.&lt;/p&gt;</comment>
                            <comment id="140484" author="greg_10gen" created="Fri, 6 Jul 2012 21:01:43 +0000"  >&lt;p&gt;I&apos;ve tried to reproduce locally on my system with the script above, but shutting down a config server doesn&apos;t seem to be triggering a problem (this is in 2.0.6, where you said the failure was immediate after terminating the config server).&lt;/p&gt;

&lt;p&gt;Would it be possible to post the same log snippet above at logLevel 5 - basically start mongos with -vvvvv?&lt;/p&gt;</comment>
                            <comment id="139963" author="jlee" created="Thu, 5 Jul 2012 17:20:39 +0000"  >&lt;p&gt;Hi Greg,&lt;/p&gt;

&lt;p&gt;I actually found this while trying to replicate some other errors we were having in one our staging environments following the Amazon explosion this weekend.  We lost 1 config server and a data node and starting seeing some strange auth issues after I recovered the db but not the config server.&lt;/p&gt;

&lt;p&gt;I&apos;m not running anything following the login under 2.0.6 - I can&apos;t connect at all after I kill the config server. &lt;/p&gt;

&lt;p&gt;In 2.0.4, if I shut down the config server I get errors trying to do a show dbs after shutting down the configserver but can still use the db and do a find.  If I kill the db ( with the configserver down ) I start gettting could not initialize cursor across all shards errors.&lt;/p&gt;

&lt;p&gt;Here&apos;s how I&apos;m setting up the test cluster:&lt;/p&gt;

&lt;p&gt;mongod --dbpath 1a --nojournal --smallfiles --oplogSize 1 --replSet shard01 --noprealloc --port 10010 --keyFile keyfile&lt;br/&gt;
mongod --dbpath 1b --nojournal --smallfiles --oplogSize 1 --replSet shard01 --noprealloc --port 10020 --keyFile keyfile&lt;br/&gt;
mongod --dbpath 1arb --nojournal --smallfiles --oplogSize 1 --replSet shard01 --noprealloc --port 10030 --keyFile keyfile&lt;/p&gt;

&lt;p&gt;mongod --dbpath 2a --nojournal --smallfiles --oplogSize 1 --replSet shard02 --noprealloc --port 20010 --keyFile keyfile&lt;br/&gt;
mongod --dbpath 2b --nojournal --smallfiles --oplogSize 1 --replSet shard02 --noprealloc --port 20020 --keyFile keyfile&lt;br/&gt;
mongod --dbpath 2arb --nojournal --smallfiles --oplogSize 1 --replSet shard02 --noprealloc --port 20030 --keyFile keyfile&lt;/p&gt;

&lt;p&gt;mongod --dbpath config01 --nojournal --smallfiles --noprealloc --configsvr --port 50010 --keyFile keyfile&lt;br/&gt;
mongod --dbpath config02 --nojournal --smallfiles --noprealloc --configsvr --port 50020 --keyFile keyfile&lt;br/&gt;
mongod --dbpath config03 --nojournal --smallfiles --noprealloc --configsvr --port 50030 --keyFile keyfile&lt;/p&gt;

&lt;p&gt;mongos --configdb localhost:50010,localhost:50020,localhost:50030 --chunkSize 1 --keyFile keyfile&lt;/p&gt;

&lt;p&gt;mongo localhost:10010/admin --eval &quot;rs.initiate({ _id:&apos;shard01&apos;, members:&lt;span class=&quot;error&quot;&gt;&amp;#91;{_id:0, host:&amp;#39;localhost:10010&amp;#39;}, {_id:1, host:&amp;#39;localhost:10020&amp;#39;}, {_id:2, host:&amp;#39;localhost:10030&amp;#39;, arbiterOnly:true}&amp;#93;&lt;/span&gt;})&quot;&lt;/p&gt;

&lt;p&gt;mongo localhost:20010/admin --eval &quot;rs.initiate({ _id:&apos;shard02&apos;, members:&lt;span class=&quot;error&quot;&gt;&amp;#91;{_id:0, host:&amp;#39;localhost:20010&amp;#39;}, {_id:1, host:&amp;#39;localhost:20020&amp;#39;}, {_id:2, host:&amp;#39;localhost:20030&amp;#39;, arbiterOnly:true}&amp;#93;&lt;/span&gt;})&quot;&lt;/p&gt;

&lt;p&gt;mongo localhost/admin --eval &quot;db.runCommand(&lt;/p&gt;
{addShard:&apos;shard01/localhost:10010,localhost:10020,localhost:10030&apos;}
&lt;p&gt;)&quot;&lt;br/&gt;
mongo localhost/admin --eval &quot;db.runCommand(&lt;/p&gt;
{addShard:&apos;shard02/localhost:20010,localhost:20020,localhost:20030&apos;}
&lt;p&gt;)&quot;&lt;br/&gt;
mongo localhost/admin --eval &quot;db.runCommand(&lt;/p&gt;
{enableSharding:&apos;test&apos;}
&lt;p&gt;)&quot;&lt;/p&gt;

&lt;p&gt;mongo localhost/test --eval &quot;for ( var i=1; i&amp;lt;=5000; i++ ){ db.foo.save({_id:i, name:Array(1000).join(&apos;a&apos;), ts: new Date() })}&quot;&lt;/p&gt;

&lt;p&gt;mongo localhost/admin --eval &quot;db.runCommand({shardCollection:&apos;test.foo&apos;, key:{_id:1}})&quot;&lt;/p&gt;

&lt;p&gt;mongo localhost/admin --eval &quot;db.addUser(&apos;admin&apos;,&apos;admin&apos;)&quot;&lt;/p&gt;</comment>
                            <comment id="139943" author="greg_10gen" created="Thu, 5 Jul 2012 16:18:44 +0000"  >&lt;p&gt;Thanks for posting the error and logs here - are you able to post a fuller log, starting ~1hr before you shut down the config server until you restart it again?  We&apos;ll try to reproduce on our side as well.&lt;/p&gt;

&lt;p&gt;Don&apos;t think this is related to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-6178&quot; title=&quot;Cannot use mongos if subset of config servers can&amp;#39;t read from or write to disk&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-6178&quot;&gt;&lt;del&gt;SERVER-6178&lt;/del&gt;&lt;/a&gt; - that issue only occurs if a shard is up and reachable but writing to disk fails -  but it should be possible to authenticate with a config server down.  &lt;/p&gt;

&lt;p&gt;What command are you running immediately after authentication?  It&apos;s not 100% clear from the log, but it could be that auth is succeeding but the next command needs to write to the config server, which should (correctly) fail.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="43812">SERVER-6378</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="17970" name="auth_with_config_down.js" size="3094" author="greg_10gen" created="Fri, 6 Jul 2012 21:01:55 +0000"/>
                            <attachment id="17972" name="mongos_local.log.gz" size="3811" author="jlee" created="Fri, 6 Jul 2012 21:26:39 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 5 Jul 2012 16:18:44 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        11 years, 32 weeks, 1 day 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-6378'>SERVER-6378</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>ian@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            11 years, 32 weeks, 1 day 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>greg_10gen</customfieldvalue>
            <customfieldvalue>jlee</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrnxiv:</customfieldvalue>

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

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

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