<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:52:45 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-643] The driver tried to connect to remote server using internal ip</title>
                <link>https://jira.mongodb.org/browse/JAVA-643</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;We are using mongo replica set on ec2, we try to use new Mongo(seeds) and external ip list as server address to get a Mongo instance from remote ec2 server, when tried to update a collection, we met with a problem that the driver failed to connect to mongo as the server hostname (external ip) changed to ec2 internal ip, so connection timeout and failed.&lt;/p&gt;

&lt;p&gt;Driver 2.7.3 is OK, Driver 2.8.0 can not find the master.&lt;/p&gt;</description>
                <environment>aws ec2</environment>
        <key id="50726">JAVA-643</key>
            <summary>The driver tried to connect to remote server using internal ip</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</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="scotthernandez">Scott Hernandez</assignee>
                                    <reporter username="roger.xia">roger xia</reporter>
                        <labels>
                    </labels>
                <created>Tue, 18 Sep 2012 02:05:42 +0000</created>
                <updated>Tue, 25 Jun 2013 16:49:41 +0000</updated>
                            <resolved>Wed, 19 Sep 2012 01:50:41 +0000</resolved>
                                    <version>2.9.0</version>
                    <version>2.9.1</version>
                                                    <component>API</component>
                    <component>Cluster Management</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="165826" author="roger.xia" created="Wed, 19 Sep 2012 01:25:02 +0000"  >&lt;p&gt;Thanks.&lt;/p&gt;</comment>
                            <comment id="165476" author="scotthernandez" created="Tue, 18 Sep 2012 13:23:29 +0000"  >&lt;p&gt;Don&apos;t use IP addresses at all. Use aliases or cnames that resolve correctly&lt;br/&gt;
in both places. As long as everything is in aws then the non-internal&lt;br/&gt;
amazon names work fine for everyone. Please read the amazon mongodb white&lt;br/&gt;
paper for an example.&lt;/p&gt;
</comment>
                            <comment id="165320" author="roger.xia" created="Tue, 18 Sep 2012 03:29:16 +0000"  >&lt;p&gt;Scott, thanks for your reply, my idea is amazon suggest users to use internal IP address across internal servers, so we configure the replica set using internal IP addresses, but in the java driver, we use external IP address list to connect, we know version 2.7.3 works. So any other suggestions you can give us rather than change the replica set configure IP addresses to external IP and grant permission on port for each of them.&lt;/p&gt;</comment>
                            <comment id="165308" author="scotthernandez" created="Tue, 18 Sep 2012 02:11:57 +0000"  >&lt;p&gt;All drivers use the addresses configured in the replica set configuration. The seed addresses are just used to get the configuration from the set.&lt;/p&gt;

&lt;p&gt;Configuring external aws addresses is how you want to do it as they resolve to internal IP addresses internally. &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|hrhson:</customfieldvalue>

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