<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:53:29 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>[JAVA-961] Add independent setting for timeout when selecting a server to operate against</title>
                <link>https://jira.mongodb.org/browse/JAVA-961</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;In 2.x, we use connectTimeout, which overloads the meaning (since we also use it for Socket connect timeout),&lt;/p&gt;

&lt;p&gt;In 3.x, it&apos;s not configurable yet, but there&apos;s an easy place to hook a value in, in BaseCluster.getServer().&lt;/p&gt;

&lt;p&gt;Possible name: serverSelectionTimeout&lt;/p&gt;


</description>
                <environment></environment>
        <key id="91722">JAVA-961</key>
            <summary>Add independent setting for timeout when selecting a server to operate against</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</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="jeff.yemin@mongodb.com">Jeffrey Yemin</assignee>
                                    <reporter username="jeff.yemin@mongodb.com">Jeffrey Yemin</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 Sep 2013 20:39:15 +0000</created>
                <updated>Fri, 4 Nov 2016 18:11:43 +0000</updated>
                            <resolved>Tue, 25 Nov 2014 13:36:11 +0000</resolved>
                                                    <fixVersion>3.0.0</fixVersion>
                                    <component>Cluster Management</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="772222" author="jeff.yemin" created="Tue, 25 Nov 2014 13:35:56 +0000"  >&lt;p&gt;Fixed in: &lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/c58856b0189d09d0d7f4156610f82802afdd4337&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/c58856b0189d09d0d7f4156610f82802afdd4337&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="432184" author="jeff.yemin" created="Fri, 27 Sep 2013 00:19:17 +0000"  >&lt;p&gt;I&apos;m not sure it&apos;s necessary to have a setting specifically for waiting for the primary.  Is it necessary for that to be different than the setting for waiting for a secondary (for secondary reads) or for waiting for a primary to read from?&lt;/p&gt;</comment>
                            <comment id="432183" author="jeff.yemin" created="Fri, 27 Sep 2013 00:17:28 +0000"  >&lt;p&gt;There are a number of places where waiting can occur:&lt;/p&gt;

&lt;ol&gt;
	&lt;li&gt;selecting a server to operate against (Not just for writes, but for reads too)&lt;/li&gt;
	&lt;li&gt;checking out a socket from the pool&lt;/li&gt;
	&lt;li&gt;connecting the socket&lt;/li&gt;
	&lt;li&gt;writing to the socket&lt;/li&gt;
	&lt;li&gt;reading from the socket&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;All of them can have independent and configurable timeouts, but only the first two can be set to zero.&lt;/p&gt;</comment>
                            <comment id="432176" author="antoine" created="Fri, 27 Sep 2013 00:01:55 +0000"  >&lt;p&gt;To reinforce the importance of this: the current behavior of waiting for connect timeout is kind of arbitrary and not ideal for env with harsh SLA.&lt;br/&gt;
It makes more sense to have a setting &apos;wait time til master&apos; during which driver would loop through and check for primary every 1s or so.&lt;br/&gt;
In many high performance case the wait would be set to 0.&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|hs42jz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>148669</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="338">Java Sprint 11</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>