<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:36:52 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-450] SlaveOk and connection pooling</title>
                <link>https://jira.mongodb.org/browse/CSHARP-450</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;Currently, servers are &quot;pooled&quot; (MongoServer.__servers) by MongoServerSettings. This leads to separate MongoServer instances to be created for different SlaveOk values, leading to having two connection pools for one server that was initialized with different slaveOk values. This by itself is perfectly fine. But, it appears that server &quot;slaveOk&quot; parameter is not used when appropriate connection is searched. Let me illustrate with an example.&lt;br/&gt;
I create server 1 with connection string that specifies slaveOk as &quot;false&quot; (the default one), then create a database, collection, and then open a cursor that has slaveOk set to true. This leads to connection pool of server that is marked as &quot;not slaveOk&quot; to contain connection that is &quot;slaveOk&quot;. While this is not an error, I still would like to ask if this is intentional, since this is a bit misleading when debugging.&lt;/p&gt;</description>
                <environment></environment>
        <key id="36660">CSHARP-450</key>
            <summary>SlaveOk and connection pooling</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="onyxmaster">Aristarkh Zagorodnikov</reporter>
                        <labels>
                            <label>question</label>
                    </labels>
                <created>Thu, 19 Apr 2012 08:37:17 +0000</created>
                <updated>Fri, 5 Apr 2019 13:58:42 +0000</updated>
                            <resolved>Thu, 19 Apr 2012 19:22:18 +0000</resolved>
                                    <version>1.4.2</version>
                                                                        <votes>0</votes>
                                    <watches>0</watches>
                                                                                                                <comments>
                            <comment id="111706" author="onyxmaster" created="Thu, 19 Apr 2012 17:57:50 +0000"  >&lt;p&gt;Thanks for the clarification and for the recommendation, Robert. We already set slaveOk on operation basis in about 80% of the cases, so it won&apos;t be an issue.&lt;/p&gt;</comment>
                            <comment id="111701" author="rstam" created="Thu, 19 Apr 2012 17:48:10 +0000"  >&lt;p&gt;Yes, it is intentional. There is nothing about a connection (a socket) that is related to slaveOk. SlaveOk is simply used to pick which server to send the query to.&lt;/p&gt;

&lt;p&gt;Since slaveOk reads are less frequent than regular reads, I would recommend setting slaveOk to false on the connection string (the default) and only set slaveOk to true on individual read operations where you want to read from a slave.&lt;/p&gt;</comment>
                    </comments>
                    <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|hrh7nr:</customfieldvalue>

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