[SERVER-4957] If shard lookup fails, retry appending the default port Created: 13/Feb/12  Updated: 15/Aug/12  Resolved: 24/Feb/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 24/Feb/12 ]

In 2.0+ we automatically append the default port to the host on replica set configuration, so it shouldn't be possible to get a host without the port anymore.

Comment by auto [ 14/Feb/12 ]

Author:

{u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: Revert "SERVER-4957: If shard lookup fails, retry appending the default port."

This reverts commit 444658ee70b45f7678fd60553e300c5f0563d017.
Branch: master
https://github.com/mongodb/mongo/commit/778223d5687f8da2c36888eeb32b314dda965efd

Comment by auto [ 13/Feb/12 ]

Author:

{u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-4957: If shard lookup fails, retry appending the default port.
Branch: master
https://github.com/mongodb/mongo/commit/444658ee70b45f7678fd60553e300c5f0563d017

Generated at Thu Feb 08 03:07:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.