<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:26: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>[DRIVERS-2610] Note that load-balanced topologies are backed by sharded clusters with replica sets</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2610</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;div class=&quot;panel&quot; style=&quot;background-color: #fafbfc;border-color: #21313c;border-style: solid;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;Quoting &lt;a href=&quot;https://www.mongodb.com/docs/manual/release-notes/3.6-upgrade-sharded-cluster/#shard-replica-sets&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Shard Replica Sets&lt;/a&gt; from the MongoDB 3.6 release notes:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Starting in MongoDB 3.6, mongod instances with the shard server role must be replica set members.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Load balancers are used with MongoDB 5.0+. Thus, drivers can assume that any load balancer is backed by a sharded cluster with replica sets and features such as change streams and transactions will be supported. It would be helpful to remind readers of this when introducing the &quot;load-balanced&quot; topology in the Unified Test Format spec.&lt;/p&gt;

&lt;p&gt;This will not require any driver changes.&lt;/p&gt;

&lt;p&gt;This issue came out of a &lt;a href=&quot;https://mongodb.slack.com/archives/C72LB5RPV/p1681973519293209&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Slack thread in #dbx-devs&lt;/a&gt;.&lt;/p&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;Driver developers.&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;The documentation for load-balanced topologies can be improved to remind developers that all LB topologies are backed by sharded clusters with replica sets.&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;No.&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;Yes.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="2319709">DRIVERS-2610</key>
            <summary>Note that load-balanced topologies are backed by sharded clusters with replica sets</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="13201">Fixed</resolution>
                                        <assignee username="jmikola@mongodb.com">Jeremy Mikola</assignee>
                                    <reporter username="jmikola@mongodb.com">Jeremy Mikola</reporter>
                        <labels>
                    </labels>
                <created>Thu, 20 Apr 2023 13:34:23 +0000</created>
                <updated>Sat, 28 Oct 2023 10:44:45 +0000</updated>
                            <resolved>Fri, 12 May 2023 02:37:10 +0000</resolved>
                                                        <component>Unified Test Runner</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="5419603" author="xgen-internal-githook" created="Fri, 12 May 2023 02:36:49 +0000"  >&lt;p&gt;Author: &lt;/p&gt;
{&apos;name&apos;: &apos;Jeremy Mikola&apos;, &apos;email&apos;: &apos;jmikola@gmail.com&apos;, &apos;username&apos;: &apos;jmikola&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2609&quot; title=&quot;Deprecate sharded-replicaset topology type and clean up redundant runOnRequirements&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2609&quot;&gt;DRIVERS-2609&lt;/a&gt;: Deprecate sharded-replicaset topology type and clean up redundant runOnRequirements (#1408)&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2609&quot; title=&quot;Deprecate sharded-replicaset topology type and clean up redundant runOnRequirements&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2609&quot;&gt;DRIVERS-2609&lt;/a&gt;: Deprecate &quot;sharded-replicaset&quot; topology type in runOnRequirements&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;MongoDB 3.6+ requires all shards to be replica sets, so there is no reason use &quot;sharded-replicaset&quot; instead of &quot;sharded&quot;.&lt;/p&gt;

&lt;p&gt;The &quot;sharded-replicaset&quot; topology type dates back to the first version of the Unified Test Format, but it&apos;s not clear it was ever truly necessary. It appears to have only been used in conjunction with 3.6+ minServerVersion requirements.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Remove redundant usage of &quot;sharded-replicaset&quot; in runOnRequirements&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;Remove redundant runOnRequirements in CSOT tests&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;A replica set will already be matched by the first runOnRequirement.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Update link to config.shards docs page in Unified Test Format spec&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2610&quot; title=&quot;Note that load-balanced topologies are backed by sharded clusters with replica sets&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2610&quot;&gt;&lt;del&gt;DRIVERS-2610&lt;/del&gt;&lt;/a&gt;: Note that LB topology implicitly has replica set shards&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/specifications/commit/474ddfcc335225df4410986be2b10ae41a736d20&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/specifications/commit/474ddfcc335225df4410986be2b10ae41a736d20&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="5364642" author="jmikola@gmail.com" created="Fri, 21 Apr 2023 04:51:27 +0000"  >&lt;p&gt;I&apos;m including this in the PR for &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2609&quot; title=&quot;Deprecate sharded-replicaset topology type and clean up redundant runOnRequirements&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2609&quot;&gt;DRIVERS-2609&lt;/a&gt; since it touches the same text:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/mongodb/specifications/pull/1408&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/specifications/pull/1408&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="5364534" author="jmikola@gmail.com" created="Fri, 21 Apr 2023 02:40:13 +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;: Thanks for clarifying.&lt;/p&gt;

&lt;p&gt;With that in mind, I think the only improvement here would be noting that rationale in the Unified Test Spec. No need to revise the Load Balancer test README.&lt;/p&gt;

&lt;p&gt;Also, it sounds like the &quot;sharded-replicaset&quot; topology may be irrelevant for any tests that require MongoDB 3.6. I&apos;ll sort that out in &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2609&quot; title=&quot;Deprecate sharded-replicaset topology type and clean up redundant runOnRequirements&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2609&quot;&gt;DRIVERS-2609&lt;/a&gt;, though.&lt;/p&gt;</comment>
                            <comment id="5363432" author="james.kovacs" created="Thu, 20 Apr 2023 18:06:50 +0000"  >&lt;p&gt;Starting in MongoDB 3.6, sharded clusters must use replica sets for the shards. It is no longer possible - even for testing - for the shards to be standalones. Thus if the topology is &lt;tt&gt;load-balanced&lt;/tt&gt; then you must be talking to one or more &lt;tt&gt;mongos&lt;/tt&gt; nodes behind it and those &lt;tt&gt;mongos&lt;/tt&gt; nodes must be talking to shard replica sets.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="2319426">DRIVERS-2609</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                            <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="10940"><![CDATA[Not Needed]]></customfieldvalue>

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

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