[PYCBC-257] Twisted timer events may sometimes not be propagated, causing hangs in the client Created: 26/Aug/14 Updated: 28/Aug/14 Resolved: 28/Aug/14
|Project:||Couchbase Python Client Library|
|Reporter:||Mark Nunberg||Assignee:||Mark Nunberg|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Due to a bug in the current implementation, a timer event which is rearmed within its C handler is not rescheduled becuase it is immediately cancelled back in the Python code. I found this issue observing that the twisted client did not properly switch over providers when one provider failed.