Intermittent "Failed to read from the socket"


#1

I am using Couchbase 2.2.0 as a custom provider for ASP.Net Session State. Intermittently there are some error happen in server. Some users experienced lost of session due to unable to retrieve session from Couchbase. Below are the error log captured. Hopefully someone can point out how to solve it.

2014-03-31 15:30:13,166 [123] ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl [(null)] <(null)> - Could not init pool.
System.IO.IOException: Failed to read from the socket ‘102.16.22.104:11210’. Error: ConnectionReset

2014-03-31 15:30:13,338 [70] ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl [(null)] <(null)> - Could not init pool.
System.IO.IOException: Failed to read from the socket ‘102.16.22.104:11210’. Error: ?

2014-03-31 15:30:57,206 [133] ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl [(null)] <(null)> - Failed to create socket. 102.16.22.104:11210
System.IO.IOException: Failed to read from the socket ‘102.16.22.104:11210’. Error: ?

2014-03-31 15:30:57,206 [163] ERROR Enyim.Caching.Memcached.MemcachedNode.InternalPoolImpl [(null)] <(null)> - Failed to create socket. 102.16.22.104:11210
System.IO.IOException: Failed to read from the socket ‘102.16.22.104:11210’. Error: ConnectionReset


#2

Hi khwong9981 -

What version of the client are you using?

Is there a stacktrace available?

-Jeff


#3

hi
hi jmorris,

CouchbaseNetClient 1.1.6
CouchbaseAspNet 1.1.0

My web application still using .Net Framework 2.0, hence the client I am using is outdated. Would it be the issue?


#4

Yeah, likely it’s an old bug. If you can upgrade, that might resolve the issue.

-Jeff


#5

Thanks. I am working on upgrade the client.

By the way, how to check if Couchbase is overloaded? As this issue usually happen during peak hours.


#6

After upgraded the client, the intermittent socket error still occurred. During the exception happen, I noticed that in the Couchbase web console, the connection count is up to 9K connections and on the diagnostic report stated

“Thu Apr 24 17:51:15.850124 Malay Peninsula Standard Time 3: Too many open connections”.

The CPU & memory is around 30% at that time, hence this eliminate the limitation of the hardware. I am suspecting this is due to maximum connection Couchbase can handle. Any information can lead me on the maximum connection supported? and how to increase the limit since the machine still capable to handle more?


#7

khwong9981 -

This sounds more like a bug perhaps…somewhere. Would you mind creating a NCBC: http://www.couchbase.com/issues/browse/NCBC ?

Also, what version of Couchbase Server are you running? Can you describe the setup (# of nodes, etc)?

Thanks,

Jeff