-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: 1.6.2
-
Component/s: Sharding
-
None
-
Environment:Tue Aug 31 19:34:31 MongoDB starting : pid=3142 port=27019 dbpath=/home/david/mongodb/config/ 64-bit
Tue Aug 31 19:34:31 db version v1.6.2-pre-, pdfile version 4.5
Tue Aug 31 19:34:31 git version: 92d5eb42af2e25ac549d7489d90261c7f6a0e767
Tue Aug 31 19:34:31 sys info: Linux domU-12-31-39-06-79-A1 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41Tue Aug 31 19:34:31 MongoDB starting : pid=3142 port=27019 dbpath=/home/david/mongodb/config/ 64-bit Tue Aug 31 19:34:31 db version v1.6.2-pre-, pdfile version 4.5 Tue Aug 31 19:34:31 git version: 92d5eb42af2e25ac549d7489d90261c7f6a0e767 Tue Aug 31 19:34:31 sys info: Linux domU-12-31-39-06-79-A1 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
-
ALL
if you enter an IP address when executing addShard, mongo assumes it's an hostname and does a DNS lookup on it. This timesout after a long time (~180 seconds or so) and the IP address is used instead, but the DNS lookup occurs every time which means the addShard command takes a long time, as does every further query to the shard.