<!-- 
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-203] Plugin load balancer for distributing reads to secondaries</title>
                <link>https://jira.mongodb.org/browse/CSHARP-203</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;Currently the C# driver is hard coded to distribute reads to secondaries (when slaveOk=true) using a round robin algorithm. However, alternative strategies exist. For example, reads could be distributed in proportion to the distance of the secondaries as measured by ping time. If the driver defined an IReadLoadBalancer interface it could provide two reference implementations: RoundRobinLoadBalancer and ProportionalDistanceLoadBalancer, and application writers could write new load balancers to meet their specific requirements.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16092">CSHARP-203</key>
            <summary>Plugin load balancer for distributing reads to secondaries</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="robert@mongodb.com">Robert Stam</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Apr 2011 21:39:01 +0000</created>
                <updated>Mon, 11 Mar 2019 18:45:08 +0000</updated>
                            <resolved>Mon, 6 Apr 2015 19:56:31 +0000</resolved>
                                    <version>1.0</version>
                                                    <component>Feature Request</component>
                                        <votes>3</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="305998" author="rstam" created="Thu, 4 Apr 2013 16:34:34 +0000"  >&lt;p&gt;Reassigning this issue to 2.0 to be either resolved or closed as won&apos;t implement.&lt;/p&gt;</comment>
                            <comment id="305997" author="rstam" created="Thu, 4 Apr 2013 16:33:43 +0000"  >&lt;p&gt;This functionality could also be achieved if we adopt the concept of binding proposed in &lt;a href=&quot;https://jira.mongodb.org/browse/CSHARP-686&quot; title=&quot;Replace RequestStart/Done with thread agnostic concepts of &amp;quot;binding&amp;quot; and &amp;quot;bound objects&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CSHARP-686&quot;&gt;&lt;del&gt;CSHARP-686&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To do your own load balancing, you would simply select a node from a cluster (using any criteria you want) and then bind a MongoDatabase instance to that node for the duration of some sequence of related operations.&lt;/p&gt;

&lt;p&gt;For the next sequence of related operations you could repeat the process of selecting a node and bind a new MongoDatabase instance to that node, and so on.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="65579">CSHARP-686</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|hrsukf:</customfieldvalue>

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