<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:18:39 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-3645] Cluster nodes are not removed on topology description change</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-3645</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;For a client pool, a mongoc_cluster_t keeps a set of nodes. Each node is associated with a server, and contains an application-use connection. Nodes are created on demand as operations need them.&lt;/p&gt;

&lt;p&gt;Cluster nodes are removed during some errors (e.g. a network error calling mongoc_cluster_disconnect_node). But a cluster node for a server will not be removed when the server is removed from the topology description.&lt;/p&gt;

&lt;p&gt;That server will no longer be eligible for server selection. So I believe the cluster node will remain around until the client is destroyed.&lt;/p&gt;

&lt;p&gt;This could be problematic for long running applications. If a server is periodically added and removed to the topology (perhaps due to poor connectivity or maintenance), many unusable cluster nodes could hang around.&lt;/p&gt;</description>
                <environment></environment>
        <key id="1336717">CDRIVER-3645</key>
            <summary>Cluster nodes are not removed on topology description change</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="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="-1">Unassigned</assignee>
                                    <reporter username="kevin.albertson@mongodb.com">Kevin Albertson</reporter>
                        <labels>
                    </labels>
                <created>Sat, 2 May 2020 07:41:17 +0000</created>
                <updated>Thu, 23 Mar 2023 21:55:53 +0000</updated>
                                                                            <component>network</component>
                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="3076541" author="jmikola@gmail.com" created="Fri, 8 May 2020 20:20:42 +0000"  >&lt;p&gt;Cross-referencing with &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-3615&quot; title=&quot;Reduce race conditions in SDAM error handling&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-3615&quot;&gt;&lt;del&gt;CDRIVER-3615&lt;/del&gt;&lt;/a&gt;, as &lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/pull/601#discussion_r421894982&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;this comment&lt;/a&gt; from its code review suggests that a change therein may address this issue.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;removing the cluster node as soon as we&apos;ve detected it is invalid might also help prevent cluster from hanging around indefinitely when the associated server description has been removed &lt;/p&gt;&lt;/blockquote&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="1313155">CDRIVER-3615</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_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6jkc:2</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>