<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:36:06 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>[CSHARP-201] When connected to a replica set a background thread should monitor the replica set</title>
                <link>https://jira.mongodb.org/browse/CSHARP-201</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;When connected to a replica set a background thread should monitor the replica set by polling isMaster for each member. If a secondary goes offline it should be removed from the list of secondaries. When a secondary comes back online (or a new member is added to the replica set) it should be automatically detected and added to the list of secondaries without having to call MongoServer.Reconnect.&lt;/p&gt;

&lt;p&gt;Not that in a heavily loaded environment failed secondaries will almost certainly be detected during a regular operation, as they are many times more frequent than the background thread polling. However, the background thread is the only way that returning or newly added secondaries will get added back to the list of secondaries.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16090">CSHARP-201</key>
            <summary>When connected to a replica set a background thread should monitor the replica set</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</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="9">Done</resolution>
                                        <assignee username="robert@mongodb.com">Robert Stam</assignee>
                                    <reporter username="robert@mongodb.com">Robert Stam</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Apr 2011 21:29:21 +0000</created>
                <updated>Thu, 2 Apr 2015 18:27:44 +0000</updated>
                            <resolved>Mon, 12 Sep 2011 21:46:01 +0000</resolved>
                                    <version>1.0</version>
                                    <fixVersion>1.2</fixVersion>
                                    <component>Feature Request</component>
                                        <votes>1</votes>
                                    <watches>0</watches>
                                                                                                                <comments>
                            <comment id="75706" author="rstam" created="Fri, 23 Dec 2011 17:57:45 +0000"  >&lt;p&gt;Note regarding the implementation of &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-201&quot; title=&quot;When connected to a replica set a background thread should monitor the replica set&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-201&quot;&gt;&lt;del&gt;CSHARP-201&lt;/del&gt;&lt;/a&gt;: the new TimerCallback only monitors individual replica set members changing state (going offline, coming back online, changing from primary to secondary, etc...).&lt;/p&gt;

&lt;p&gt;See also &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-370&quot; title=&quot;Setting a node as Hidden doesn&amp;#39;t propagate to C# drivers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-370&quot;&gt;&lt;del&gt;CSHARP-370&lt;/del&gt;&lt;/a&gt;, which is related to two additional issues:&lt;/p&gt;

&lt;p&gt;1. Detecting when replica set members are added or removed from the set (handling a reconfig without needing to call Reconnect)&lt;br/&gt;
2. Handling hidden members a little better&lt;/p&gt;</comment>
                            <comment id="53556" author="rstam" created="Mon, 12 Sep 2011 21:46:01 +0000"  >&lt;p&gt;The TimerCallback in MongoServerInstance now verifies the state of the replica set member every time the timer fires. Any changes in the state of a MongoServerInstance is reflected back to the state of the MongoServer via the InstanceStateChanged event.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="27109">CSHARP-370</issuekey>
        </issuelink>
                            </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|hrh93r:</customfieldvalue>

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