<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:08:33 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-5322] better messaging when cannot connect to mongos when shard is down</title>
                <link>https://jira.mongodb.org/browse/SERVER-5322</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Resolved current issue - leaving open for better reporting when mongos auth fails to a sharded database.&lt;/p&gt;

&lt;p&gt;=====&lt;/p&gt;

&lt;p&gt;See &lt;a href=&quot;https://groups.google.com/forum/?fromgroups#!topic/mongodb-user/NREVf6tuvbA&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://groups.google.com/forum/?fromgroups#!topic/mongodb-user/NREVf6tuvbA&lt;/a&gt;&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;$ mongo localhost:27123/db -uusername -ppassword&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;MongoDB shell version: 2.0.3&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;connecting to: localhost:27123/db&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;Wed Mar 14 11:01:47 uncaught exception: error { &quot;$err&quot; : &quot;socket exception&quot;, &quot;code&quot; : 11002 }&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;exception: login failed&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;$&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;Seems related to &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-3763&quot; title=&quot;when one shard goes down, mongos starts returning failure in getlasterror for all the shards, to already connected client.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-3763&quot;&gt;&lt;del&gt;SERVER-3763&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-4643&quot; title=&quot;one of the shard is down&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-4643&quot;&gt;&lt;del&gt;SERVER-4643&lt;/del&gt;&lt;/a&gt;, but they are on 2.0.3 and it isn&apos;t working.&lt;/p&gt;</description>
                <environment></environment>
        <key id="33075">SERVER-5322</key>
            <summary>better messaging when cannot connect to mongos when shard is down</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</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="kristina">Kristina Chodorow</reporter>
                        <labels>
                    </labels>
                <created>Thu, 15 Mar 2012 17:21:35 +0000</created>
                <updated>Mon, 20 Jul 2015 22:23:55 +0000</updated>
                            <resolved>Mon, 20 Jul 2015 22:23:55 +0000</resolved>
                                                                    <component>Security</component>
                    <component>Sharding</component>
                                        <votes>2</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="970448" author="schwerin" created="Mon, 20 Jul 2015 22:23:55 +0000"  >&lt;p&gt;As of 2.6, auth data is stored in the config database, not in the shards, so this error should have gone away.&lt;/p&gt;</comment>
                            <comment id="131758" author="greg_10gen" created="Wed, 13 Jun 2012 14:09:41 +0000"  >&lt;p&gt;Changed priority to minor, this has become a log issue.  &lt;/p&gt;</comment>
                            <comment id="111388" author="vasyl" created="Wed, 18 Apr 2012 22:10:33 +0000"  >&lt;p&gt;Thanks Greg! Appreciate it.&lt;/p&gt;

&lt;p&gt;Vasyl&lt;/p&gt;</comment>
                            <comment id="111386" author="greg_10gen" created="Wed, 18 Apr 2012 22:04:01 +0000"  >&lt;p&gt;Agree - updated.  &lt;/p&gt;</comment>
                            <comment id="111291" author="vasyl" created="Wed, 18 Apr 2012 18:33:30 +0000"  >&lt;p&gt;You&apos;re right Greg. &lt;br/&gt;
This makes sense in some point&lt;/p&gt;

&lt;p&gt;I think auth=off &amp;amp; no --keyFile option should be mentioned in failover part then&lt;br/&gt;
(3. Failure of all mongod servers comprising a shard.)&lt;br/&gt;
&lt;a href=&quot;http://www.mongodb.org/display/DOCS/Sharding+and+Failover&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.mongodb.org/display/DOCS/Sharding+and+Failover&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Vasyl&lt;/p&gt;</comment>
                            <comment id="111287" author="greg_10gen" created="Wed, 18 Apr 2012 18:25:36 +0000"  >&lt;p&gt;I&apos;m not yet convinced this is actually the best way forward - for example some authentication data sits on the config servers, which are always up by definition if the cluster is up.  Also, there&apos;s always the ability to add more replica set servers to the primary shard, to get whatever level of redundancy you think is needed.  Spreading the auth data around causes a lot of problems, in terms of migrations, shards added / removed, stale auth data, etc - if increasing uptime is the goal, there are a lot of options.  &lt;/p&gt;

&lt;p&gt;Feel free to open an improvement ticket though, to tell us how you think things should behave and we could have more discussion there.&lt;/p&gt;</comment>
                            <comment id="111014" author="vasyl" created="Wed, 18 Apr 2012 08:01:24 +0000"  >&lt;p&gt;Hey Greg!&lt;/p&gt;

&lt;p&gt;Yep, I&apos;m totaly agree - auth feature needs to be improved.&lt;/p&gt;

&lt;p&gt;We do using repSets so we are safe in some point. But not if primary shard goes down. &lt;br/&gt;
It would be extremely nice to allow end user resides on other shard(s) access their data in such case&lt;/p&gt;

&lt;p&gt;Could this be tracked in jira, pls?&lt;br/&gt;
I mean the  the idea of sharing system users among all shards, b/c of single point of failure?&lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
Vasyl&lt;/p&gt;


</comment>
                            <comment id="108394" author="greg_10gen" created="Tue, 10 Apr 2012 18:35:22 +0000"  >&lt;p&gt;&amp;gt; If #1 shard goes down - ##2-100 shards will become unavailable for the end clients - &lt;/p&gt;

&lt;p&gt;This is somewhat true - any connections that are currently open will still be authenticated, and ideally the drivers support connection pooling so new connections aren&apos;t required for each request.     Also, in any production setup we highly recommend replica set shards so that there&apos;s never a need to have a shard completely down.  With the patch provided in &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-5406&quot; title=&quot;mongos does not allow new connections for 30 seconds-&amp;gt;a couple minutes when an rs member goes down&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-5406&quot;&gt;&lt;del&gt;SERVER-5406&lt;/del&gt;&lt;/a&gt;, a secondary should always be available for reading the auth info.&lt;/p&gt;

&lt;p&gt;Agree in general though, authentication is a fairly new feature and we want to make sure we eliminate bottlenecks wherever possible.&lt;/p&gt;</comment>
                            <comment id="108169" author="vasyl" created="Tue, 10 Apr 2012 09:15:24 +0000"  >&lt;p&gt;Hello Greg!&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;I believe this is actually works-as-designed if the full shard is down, we unfortunately can&apos;t authorize access to the db without the security info stored on the primary shard&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;i had same thoughts due to this issue&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;Users are stored on the primary shard so authentication can be done there&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;http://www.mongodb.org/display/DOCS/Security+and+Authentication#SecurityandAuthentication-ReplicaSetandShardingAuthentication&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;and i think it would be good idea to share system users among all shards, b/c of single point of failure&lt;br/&gt;
example: 100 shards (#1 shard is primary - system accounts stored on it) - if #1 shard goes down - ##2-100 shards will become unavailable for the end clients.&lt;/p&gt;

&lt;p&gt;thanks&lt;br/&gt;
vasyl&lt;/p&gt;</comment>
                            <comment id="106947" author="greg_10gen" created="Thu, 5 Apr 2012 14:21:15 +0000"  >&lt;p&gt;Leaving open for fix of better messaging.&lt;/p&gt;</comment>
                            <comment id="106946" author="greg_10gen" created="Thu, 5 Apr 2012 14:20:27 +0000"  >&lt;p&gt;After more testing/reproducing last night as well, this is also works-as-designed when starting mongos without a replica set primary on the shard with authentication data.  When first starting mongos, we need to be able to connect to a replica set primary in order to ensure we aren&apos;t seeing a stale minority of nodes that have been partitioned off the replica set.  &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-5406&quot; title=&quot;mongos does not allow new connections for 30 seconds-&amp;gt;a couple minutes when an rs member goes down&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-5406&quot;&gt;&lt;del&gt;SERVER-5406&lt;/del&gt;&lt;/a&gt; has a patch for the case when an existing mongos has a primary down, or a new mongos just has a secondary issue.  &lt;/p&gt;</comment>
                            <comment id="106820" author="greg_10gen" created="Thu, 5 Apr 2012 03:30:44 +0000"  >&lt;p&gt;I believe this is actually works-as-designed if the full shard is down, we unfortunately can&apos;t authorize access to the db without the security info stored on the primary shard.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="34702">SERVER-5406</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 4 Apr 2012 19:36:41 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        8 years, 30 weeks, 2 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>false</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>schwerin@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            8 years, 30 weeks, 2 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>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>greg_10gen</customfieldvalue>
            <customfieldvalue>kristina</customfieldvalue>
            <customfieldvalue>vasyl</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hro9fz:</customfieldvalue>

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

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

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