[CSHARP-879] No Such Host Is Known / Server IP ***.****.****.**** is no longer connected Created: 17/Dec/13  Updated: 20/Mar/14  Resolved: 17/Dec/13

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 1.8.3
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Ryan Lamvohee Assignee: Unassigned
Resolution: Done Votes: 0
Labels: AWS, Azure, ConnectionFailure, EC2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Local, Azure, EC2


Attachments: PNG File MongoErrors.png    

 Description   

I've attached a code snippet here http://pastebin.com/L9DQupxZ

We've been experiencing connection issues in our production application since switching to C# for our main mongo processing tool.

After a large read i.e select all from table (8000 Documents) the c# driver throws a 'no host is known' error and crashes or a 'server ip- xxx.xxx.xxx is no longer connected'

In the aftermath of this event I decided to test our database by inserting a large number of records using a very simple c# console application as shown in the screenshot attached it makes about 100 - 150 inserts and then throws the same error continues to fail inserts a few more records and then fails constantly forever.

This occurs on a Mongo DB instance Setup on Amazons EC2 it also Occurs on a free MongoLab DB and a High Availability MongoLab DB



 Comments   
Comment by Craig Wilson [ 17/Dec/13 ]

Glad it all worked out...

Comment by Ryan Lamvohee [ 17/Dec/13 ]

Hello Everyone,

We've resolved this issue now.

The problem was we used the mongo console app to create the replica sets on the databases which put in the local machines ec2 ip address in the format of ip-xxx-xxx-xxx-xxx:port when switching this out to the public Elastic IP Address the connection issues resolved themselvs.

Generated at Wed Feb 07 21:38:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.