-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.4.2
-
Component/s: Replication
-
None
-
Environment:Unix Operating system(CentOS 6.4)
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
In my project MongoDb is installed in our software.I created 3 Machines in cloud Using VMWare. Regarding my testbed I can say that, I have ESXI software installed in UCS-Blade and above that,we are creating our VM Machines with our created software(MongoDB 2.4.6 is already pre-installed in our software).
For checking cluster creation,I created 3 VM Machines and created cluster among themselves.I created a database and put some data in primary and its successfully reflecting in other Machines.
Then to check replication,I switched off the primary VM and other machine from secondary become primary as excepted.
But when I created the machine by using the same ip(The IP of the Machine which I deleted Previously),in mongodb its giving fs):FATAL error.It is not going to secondary VM as excepted.
If I type rs.status() in that machine its always telling its in syncing state.
Request you to kindly help on this regard or if its a known bug,pls give me the bug ID.