[PYCBC-11] a disconnected or misbehaving connection may cause instability in the client library Created: 22/Aug/11 Updated: 04/May/13 Resolved: 04/May/13 |
|
| Status: | Closed |
| Project: | Couchbase Python Client Library |
| Component/s: | library |
| Affects Version/s: | None |
| Fix Version/s: | 0.9.0 |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Ingenthron | Assignee: | Mark Nunberg |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
This bug has not actually been observed, but it is expected that something like a stale connection (one where the server is gone, but no TCP timeout or RST packet has been received) could cause the client to continue to write to something not there forever. The client library should be more resiliant.
|
| Comments |
| Comment by Matt Ingenthron [ 13/Oct/11 ] |
| I believe this is closeable, correct? |