-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 1.6.3
-
Component/s: Replication
-
None
-
Environment:Linux 2.6.34.2 with Ubuntu Lucid Lynx userland, mongodb package from 10gen on a dual core 64bits EC2 server. (m1.large)
-
Linux
Given an empty mongodb server launched with --replSet.
If you immediately run rs.initiate(); when the server start to accept connections on port 27017 the command fails.
A quick look over the source code show that at this time ReplSet::startupStatus is different from ReplSet::EMPTYCONFIG as it should be.
If you wait 5 seconds after the server start to accept connections to run the command then it succeed.
I expect the command to succeed as soon as the server start to accept connections. It breaks automation scripts.
Please find attached the console output.