<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:17:44 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>[CDRIVER-3333] Session is not pinned when only a single mongos is present</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-3333</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;When running a sharded transaction in a sharded cluster with a single mongos node, the session is not pinned to that server. Since topology scans may reveal additional mongos nodes, this can cause issues later. The session needs to be pinned even when running with a single mongos node.&lt;/p&gt;

&lt;p&gt;I&apos;ve also added a SPEC ticket to clarify this in the transaction spec: SPEC-1428.&lt;/p&gt;</description>
                <environment></environment>
        <key id="904781">CDRIVER-3333</key>
            <summary>Session is not pinned when only a single mongos is present</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="13202">Works as Designed</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="andreas.braun@mongodb.com">Andreas Braun</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Aug 2019 14:14:52 +0000</created>
                <updated>Fri, 27 Oct 2023 13:14:11 +0000</updated>
                            <resolved>Mon, 26 Aug 2019 13:47:02 +0000</resolved>
                                    <version>1.15.0</version>
                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="2386442" author="andreas.braun" created="Mon, 26 Aug 2019 13:47:02 +0000"  >&lt;p&gt;As per my &lt;a href=&quot;https://github.com/mongodb/mongo-php-driver/pull/1014#discussion_r317610070&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;comment in the PR&lt;/a&gt;, I&apos;m closing this as &quot;Works as Designed&quot;. Since the initial topology type is set to &quot;Single&quot; if only a single mongos was found in the connection string or via SRV discovery and this disables polling for additional members, I don&apos;t see why a session should be pinned in this instance.&lt;/p&gt;</comment>
                            <comment id="2384804" author="kevin.albertson" created="Fri, 23 Aug 2019 18:36:21 +0000"  >&lt;p&gt;Commented in the PR discussion. I validated with the same manual tests that if we enter SRV polling because the topology type is sharded, we stay in sharded even if the host list reduces to one host during polling.&lt;/p&gt;</comment>
                            <comment id="2384715" author="jmikola@gmail.com" created="Fri, 23 Aug 2019 17:47:30 +0000"  >&lt;p&gt;Per &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kevin.albertson&quot; class=&quot;user-hover&quot; rel=&quot;kevin.albertson&quot;&gt;kevin.albertson&lt;/a&gt;&apos;s response in &lt;a href=&quot;https://github.com/mongodb/mongo-php-driver/pull/1014#discussion_r317165306&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;mongodb/mongo-php-driver#1014&lt;/a&gt;, I think this can be resolved &quot;Works as Designed&quot;.  In summary: when the URI includes only a single host (and no &lt;tt&gt;replSet&lt;/tt&gt; option), libmongoc initializes the topology type to single. Session pinning is only done for sharded topology types.&lt;/p&gt;

&lt;p&gt;Kevin also clarified that if the initial topology type is sharded (i.e. connection string includes multiple mongos hosts), but SRV polling reduces the list of known mongos hosts down to one, the topology type will remain sharded and pinning will still occur. That is relevant since SRV polling could later pick up additional mongos hosts and a pinned session would be quite relevant.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=kevin.albertson&quot; class=&quot;user-hover&quot; rel=&quot;kevin.albertson&quot;&gt;kevin.albertson&lt;/a&gt;: Do you want to leave this issue open to double-check the above? You did say &quot;IIUC&quot; in the comment so we should probably make sure if there&apos;s any doubt.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                        </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_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hvba93:</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>