<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:22:34 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>[DRIVERS-910] Allow MongoClient to automatically transition from replica set to sharded endpoint without restarts</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-910</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;div class=&quot;panel&quot; style=&quot;background-color: #fafbfc;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelContent&quot; style=&quot;background-color: #fafbfc;&quot;&gt;
&lt;h3&gt;&lt;a name=&quot;Summary&quot;&gt;&lt;/a&gt;&lt;b&gt;Summary&lt;/b&gt;&lt;/h3&gt;

&lt;p&gt;Definitions:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;b&gt;router endpoint&lt;/b&gt; - server endpoint that routes requests to shards (i.e. mongos)&lt;/li&gt;
	&lt;li&gt;&lt;b&gt;replica set endpoint&lt;/b&gt; - server endpoint that emulates a replica set or standalone (i.e. mongod)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Starting in 8.0, sharded clusters will be the only supported topology in MongoDB. To allow customers currently using a MongoDB replica set to migrate to MongoDB 8.0 without needing to reconfigure their applications, the server team will build a &quot;replica set endpoint&quot; that makes a single-shard cluster appear to be a replica set (PM-2965). However, there are limitations to the replica set endpoint:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;It can only be used with single-shard clusters, so customers have to switch to the router endpoint if they want to add more shards (e.g. to scale horizontally).
	&lt;ul&gt;
		&lt;li&gt;Note that the there have been discussions about supporting multi-shard clusters with the replica set endpoint, but it&apos;s currently not in the scope of PM-2965. In any case, horizontal scalability will likely still be limited for customers using the replica set endpoint.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;It will likely be removed with a future version of MongoDB (9.0 or later), so probably can&apos;t be used indefinitely.
	&lt;ul&gt;
		&lt;li&gt;It&apos;s not decided when the replica set endpoint feature will be removed.&lt;br/&gt;
As a result, customers may eventually be motivated or required to stop using the replica set endpoint.&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;To switch to the router endpoint, customers using existing drivers will have to update their connection string and restart their applications. We want to offer customers a better migration experience that doesn&apos;t require reconfiguring and restarting their application to switch to the router endpoint.&lt;/p&gt;

&lt;p&gt;Updated from the original description:&lt;br/&gt;
&lt;blockquote&gt;&lt;p&gt;It might be useful to allow a MongoClient to survive cluster topology changes from a replica set to a sharded cluster (or vice versa). For example, client is connected to mongoses A and B and an admin restarts A and B as a replica set, the client could rediscover A and B as replica set members.&lt;/p&gt;

&lt;p&gt;Currently &lt;a href=&quot;https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring.rst#topologytype-table&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;the SDAM spec&lt;/a&gt; does not allow this. When a MongoClient is connected to a replica set, it will remove servers that are discovered to be mongos nodes. When a MongoClient is connected to a sharded cluster (a set of mongos nodes), it will remove servers that are not mongos nodes.&lt;/p&gt;

&lt;p&gt;I can imagine this addition to the SDAM spec would allow it:&lt;/p&gt;&lt;/blockquote&gt;If all nodes are removed from the Topology, clients MUST reset the TopologyType to Unknown and rediscover the original seed addresses.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Originally requested in: &lt;a href=&quot;https://jira.mongodb.org/browse/PYTHON-2131&quot; title=&quot;Driver connect replica set failed when changing from sharded cluster without address change&quot; class=&quot;issue-link&quot; data-issue-key=&quot;PYTHON-2131&quot;&gt;&lt;del&gt;PYTHON-2131&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;h3&gt;&lt;a name=&quot;Motivation&quot;&gt;&lt;/a&gt;&lt;b&gt;Motivation&lt;/b&gt;&lt;/h3&gt;
&lt;h4&gt;&lt;a name=&quot;Whoistheaffectedenduser%3F&quot;&gt;&lt;/a&gt;Who is the affected end user?&lt;/h4&gt;

&lt;p&gt;Customers who upgrade existing replica sets to MongoDB 8.0 or who chose use the new replica set endpoint for a new MongoDB 8.0 cluster (see PM-2965).&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Howdoesthisaffecttheenduser%3F&quot;&gt;&lt;/a&gt;How does this affect the end user?&lt;/h4&gt;

&lt;p&gt;Customers may delay migrating off the replica set endpoint, reducing their motivation to horizontally scale their clusters or preventing them from migrating to a future MongoDB version that doesn&apos;t have the replica set endpoint feature.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Howlikelyisitthatthisproblemorusecasewilloccur%3F&quot;&gt;&lt;/a&gt;How likely is it that this problem or use case will occur?&lt;/h4&gt;

&lt;p&gt;All customers using the MongoDB 8.0 replica set endpoint will eventually need to switch to the router endpoint.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Iftheproblemdoesoccur%2Cwhataretheconsequencesandhowseverearethey%3F&quot;&gt;&lt;/a&gt;If the problem does occur, what are the consequences and how severe are they?&lt;/h4&gt;

&lt;p&gt;Customers who want or need to switch to the router endpoint must change their connection string and restart their applications to re-initialize the &lt;tt&gt;MongoClient&lt;/tt&gt;.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisissueurgent%3F&quot;&gt;&lt;/a&gt;Is this issue urgent?&lt;/h4&gt;

&lt;p&gt;This feature will be useful when MongoDB 8.0 is released. It will become even more useful when a future MongoDB version is released that removes the replica set endpoint feature.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisticketrequiredbyadownstreamteam%3F&quot;&gt;&lt;/a&gt;Is this ticket required by a downstream team?&lt;/h4&gt;

&lt;p&gt;No.&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Isthisticketonlyfortests%3F&quot;&gt;&lt;/a&gt;Is this ticket only for tests?&lt;/h4&gt;

&lt;p&gt;No.&lt;/p&gt;
&lt;h3&gt;&lt;a name=&quot;AcceptanceCriteria&quot;&gt;&lt;/a&gt;&lt;b&gt;Acceptance Criteria&lt;/b&gt;&lt;/h3&gt;

&lt;p&gt;To allow migrating from the replica set endpoint to the router endpoint, drivers must be able to:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Discover the router endpoint(s) somehow.&lt;/li&gt;
	&lt;li&gt;Give customers some way to configure whether or not they want their applications to automatically switch to the router endpoint(s), if available.&lt;/li&gt;
	&lt;li&gt;Update the current topology from replica set or standalone to sharded cluster.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;Open questions:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Should we try to make this work for pre-8.0 MongoDB versions?&lt;/li&gt;
	&lt;li&gt;Should we try to make this work for self-hosted databases or Atlas only?&lt;/li&gt;
	&lt;li&gt;Are there other topology transitions that may become important in the future?&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;
	&lt;ol&gt;
		&lt;li&gt;Future customers may switch from sharded to load-balanced clusters. Should we try to support no-restart transitions from sharded to load-balanced? (suggested by &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=tyler.brock%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;tyler.brock@mongodb.com&quot;&gt;tyler.brock@mongodb.com&lt;/a&gt;)&lt;/li&gt;
	&lt;/ol&gt;
	&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="1162490">DRIVERS-910</key>
            <summary>Allow MongoClient to automatically transition from replica set to sharded endpoint without restarts</summary>
                <type id="11" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14707&amp;avatarType=issuetype">Epic</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="matt.dale@mongodb.com">Matt Dale</assignee>
                                    <reporter username="shane.harvey@mongodb.com">Shane Harvey</reporter>
                        <labels>
                            <label>invisiblesharding-fy24q2</label>
                            <label>invisiblesharding-m1</label>
                    </labels>
                <created>Wed, 19 Feb 2020 19:51:49 +0000</created>
                <updated>Thu, 21 Dec 2023 20:11:32 +0000</updated>
                                                                <component>SDAM</component>
                                        <votes>1</votes>
                                    <watches>27</watches>
                                                                                                                <comments>
                            <comment id="5139887" author="garaudy.etienne" created="Wed, 25 Jan 2023 15:44:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rachelle.palmer%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;rachelle.palmer@mongodb.com&quot;&gt;rachelle.palmer@mongodb.com&lt;/a&gt; &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jeff.yemin%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;jeff.yemin@mongodb.com&quot;&gt;jeff.yemin@mongodb.com&lt;/a&gt; I don&apos;t think this is strictly 7.0 required. But definitely before 8.0 because the sooner this is out the higher the likelihood folks have a driver with this before switching to sharding in 8.0+ clusters. Can it be done immediately post-7.0?&lt;/p&gt;</comment>
                            <comment id="5108792" author="garaudy.etienne" created="Thu, 12 Jan 2023 13:44:07 +0000"  >&lt;p&gt;For INIT-319, we&apos;re going to make any customer who upgrades to 8.0 switch to sharding, so it will greatly increase the number of folks who run into this issue. But if we do this before then, we&apos;ll the increasing number of folks who voluntarily switch to sharding today. So it&apos;s both.&#160;&lt;/p&gt;</comment>
                            <comment id="5107807" author="garaudy.etienne" created="Thu, 12 Jan 2023 00:49:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=james.kovacs%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;james.kovacs@mongodb.com&quot;&gt;james.kovacs@mongodb.com&lt;/a&gt; The emulation layer is strictly for apps that need the exact same single-threaded op latency and can&apos;t create enough concurrency in their system. We expect less than 5% of users to use the emulation layer.&#160;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jeff.yemin%40mongodb.com&quot; class=&quot;user-hover&quot; rel=&quot;jeff.yemin@mongodb.com&quot;&gt;jeff.yemin@mongodb.com&lt;/a&gt; this is still required for all customers upgrading to sharding, no? So the sooner the better.&#160;&lt;/p&gt;</comment>
                            <comment id="4369211" author="dbeng-pm-bot" created="Tue, 22 Feb 2022 18:23:49 +0000"  >&lt;p&gt;If you are not logged in, you can view the tickets in this epic by following &lt;a href=&quot;https://jira.mongodb.org/issues/?jql=%22Epic%20Link%22%20%3D%20DRIVERS-910&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;this link&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="4300712" author="dbeng-pm-bot" created="Wed, 19 Jan 2022 17:18:44 +0000"  >&lt;p&gt;If you are not logged in, you can view the tickets in this epic by following &lt;a href=&quot;https://jira.mongodb.org/issues/?jql=%22Epic%20Link%22%20%3D%20DRIVERS-910&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;this link&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="4239869" author="behackett" created="Thu, 9 Dec 2021 22:34:18 +0000"  >&lt;p&gt;We can&apos;t poll srv for replica set changes, that would mean we have two sources of &quot;truth&quot;, when in reality the replica set itself is the only source of truth. I suppose we could always poll srv waiting to see if a mongos ever magically appears in the result, but it would be better if we were given a signal about what we should do, perhaps through TXT records?&lt;/p&gt;</comment>
                            <comment id="4239768" author="alex.bevilacqua" created="Thu, 9 Dec 2021 21:56:53 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=behackett&quot; class=&quot;user-hover&quot; rel=&quot;behackett&quot;&gt;behackett&lt;/a&gt; I wonder if limiting the scope here to poll SRV records regardless of topology type would make more sense. Having an application that only specifies a seed list wouldn&apos;t really be able to connect to anything different, but an SRV records that refreshes with mongos hosts after an Atlas conversion could theoretically work here.&lt;/p&gt;</comment>
                            <comment id="4239747" author="behackett" created="Thu, 9 Dec 2021 21:48:26 +0000"  >&lt;p&gt;There are a few tricky things here. For transition from replica set to sharded cluster, the client is already connected to a valid replica set, that will presumably just become the first shard in the sharded cluster. How do we signal the driver that it should disconnect from the replica set it&apos;s already talking to, and won&apos;t be restarted, and instead connect to a list of mongos instances without a restart?  &lt;/p&gt;</comment>
                            <comment id="2885444" author="oleg.pudeyev" created="Wed, 19 Feb 2020 20:19:25 +0000"  >&lt;p&gt;Currently according to the sdam spec the state of a topology having no servers is a terminal state. Ruby provides diagnostics (warn level logging) when this state is reached, to inform the user of possible misconfiguration of their deployment.&lt;/p&gt;

&lt;p&gt;In the linked python ticket, the submitter requests the following:&lt;/p&gt;

&lt;p&gt;&amp;gt; I want to convert the sharded cluster in our production environment to a replica set, but i don&apos;t want to change the connection uri in the application configuration.&lt;/p&gt;

&lt;p&gt;Note that SPEC-1248 will make it possible for all drivers to automatically detect both replica sets and sharded clusters from the same URI, hence an application restart would be the only thing needed to use the new deployment (currently depending on the driver, application reconfiguration may also be required; per Shane&apos;s comment in the linked ticket, it seems that applications using the Python driver do indeed need to be reconfigured).&lt;/p&gt;

&lt;p&gt;So, it seems that the change from sharded to replica set topology in a running application is not actually a customer request in this case.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10620">
                    <name>Issue split</name>
                                            <outwardlinks description="split to">
                                        <issuelink>
            <issuekey id="2391975">CDRIVER-4683</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391980">CSHARP-4717</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391977">CXX-2714</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391981">GODRIVER-2905</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391982">JAVA-5071</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391986">MOTOR-1153</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391984">NODE-5453</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391990">PHPLIB-1195</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391988">PYTHON-3836</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391992">RUBY-3297</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2391994">RUST-1702</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="1161375">PYTHON-2131</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2457487">DRIVERS-2740</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="2331464">DRIVERS-2622</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                    <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5002K00000zfEjxQAE, 5002K000011gjMaQAI, 5006R00001mESXkQAO]]]></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_10951" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Driver Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10748"><![CDATA[Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_23952" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Driver Compliance</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[<style type='text/css'>
         #scriptField, #scriptField *{
                border: 1px solid black;
            }

            #scriptField{
                border-collapse: collapse;
            }

            #scriptField td {
                text-align: center; /* Center-align text in table cells */
            }

            #scriptField td.key {
                text-align: left; /* Left-align text in the Key column */
            }

            #scriptField a {
                text-decoration: none; /* Remove underlines from links */
                border: none; /* Remove border from links */
            }
            
            /* Add green background color to cells with FixVersion */
            #scriptField td.hasFixVersion {
                background-color: #00FF00; /* Green color code */
            }

            /* Center-align the first row headers */
            #scriptField th {
                text-align: center;
            }
        </style>
<table id='scriptField'>
  <tr>
    <th>Key</th>
    <th>Status/Resolution</th>
    <th>FixVersion</th>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/CDRIVER-4683'>CDRIVER-4683</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/CXX-2714'>CXX-2714</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/CSHARP-4717'>CSHARP-4717</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/GODRIVER-2905'>GODRIVER-2905</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/JAVA-5071'>JAVA-5071</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/NODE-5453'>NODE-5453</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/MOTOR-1153'>MOTOR-1153</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/PYTHON-3836'>PYTHON-3836</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/PHPLIB-1195'>PHPLIB-1195</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/RUBY-3297'>RUBY-3297</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
  <tr>
    <td class='key'>
      <a href='https://jira.mongodb.org/browse/RUST-1702'>RUST-1702</a>
    </td>
    <td>Blocked</td>
    <td class=''></td>
  </tr>
</table>]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_18362" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Engineering Lead</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>matt.dale@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10860" key="com.pyxis.greenhopper.jira:gh-epic-color">
                        <customfieldname>Epic Colour</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ghx-label-4</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10858" key="com.pyxis.greenhopper.jira:gh-epic-label">
                        <customfieldname>Epic Name</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Allow MongoClient to survive cluster topology changes from sharded cluster to replica set</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10859" key="com.pyxis.greenhopper.jira:gh-epic-status">
                        <customfieldname>Epic Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10640"><![CDATA[To Do]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_23450" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Initiative Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[
                            <a href="https://jira.mongodb.org/browse/INIT-5">INIT-5</a> - Make sharding invisible
                    ]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_18358" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Product Manager</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>rachelle.palmer@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18359" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Program Manager</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>esha.bhargava@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_21553" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Quarter</customfieldname>
                        <customfieldvalues>
                                        <label>FY25Q2</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr1o2o:r</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>