[NCBC-126] Implement keep-alive logic for data connections Created: 27/Sep/12 Updated: 28/Oct/13 Resolved: 28/Oct/13
|Project:||Couchbase .NET client library|
|Reporter:||Perry Krug||Assignee:||Jeff Morris|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
A customer has been experiencing connection resets due to a firewall in place between the application servers and Couchbase closing idle connections.
While we have a heartbeat on 8091, we do not for 11210.
This is necessary to prevent the firewall from seeing these connections as idle.
|Comment by Alejandro [ 28/Nov/12 ]|
|Will this fix be also implemented for Java libraries?|
|Comment by Pieter Rautenbach [ 09/Jul/13 ]|
We experience a similar issue. The fact that the built-in data structure used is a stack is contributing to the issue. If connections were rotated, you wouldn't get that the top most connections on the stack would be used most, while others starve or get stale. Of course, if the client-server connections are all used (i.e. a very busy application), then it would likely not matter that much. See |
|Comment by Jeff Morris [ 28/Oct/13 ]|