<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:21:04 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>[DRIVERS-237] Include replication lag as a method for server selection</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-237</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;It would be great to have the option to specify the maximum acceptable replication lag for secondary server selection in the same way that localThresholdMS/secondary_acceptable_latency_ms is provided.&lt;/p&gt;</description>
                <environment></environment>
        <key id="212786">DRIVERS-237</key>
            <summary>Include replication lag as a method for server selection</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="3">Duplicate</resolution>
                                        <assignee username="barrie">Barrie Segal</assignee>
                                    <reporter username="markunsworth">Mark Unsworth</reporter>
                        <labels>
                            <label>Driver</label>
                            <label>Replication</label>
                            <label>mongos</label>
                            <label>read-preferences</label>
                            <label>replicaset</label>
                    </labels>
                <created>Wed, 24 Jun 2015 17:40:18 +0000</created>
                <updated>Tue, 4 Oct 2016 20:23:59 +0000</updated>
                            <resolved>Tue, 4 Oct 2016 20:23:59 +0000</resolved>
                                                                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="1400114" author="jeff.yemin" created="Tue, 4 Oct 2016 20:23:52 +0000"  >&lt;p&gt;Closing as a duplicate of &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-293&quot; title=&quot;Allow users to set a limit on acceptable staleness&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-293&quot;&gt;&lt;del&gt;DRIVERS-293&lt;/del&gt;&lt;/a&gt;, in which the maxStalenessMS option was added to the read preference.&lt;/p&gt;</comment>
                            <comment id="949600" author="behackett" created="Wed, 24 Jun 2015 18:31:13 +0000"  >&lt;p&gt;This couldn&apos;t be implemented using current releases of MongoDB, at least not completely. There are at least two problems that would have to be resolved in the server first:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The replication lag information would have to be readily available to all authenticated users. Currently this information comes from the replSetGetStatus command, which requires the clusterManager permission to run.&lt;/li&gt;
	&lt;li&gt;mongos would have to accept the acceptable replication lag as a $readPreference option, and apply it when choosing secondaries.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;On top of this, drivers monitor connected servers on a fixed frequency (10 seconds), but replication lag tends to spike for short periods of time. That monitoring frequency might not be granular enough. This would not be a solution for trying to force read-your-writes consistency while reading from secondaries.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="269200">DRIVERS-293</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|hsamm7:</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>