[PCBC-159] incorrect timeout exceptions during required-durability function tests Created: 05/Dec/12  Updated: 11/Dec/12  Resolved: 05/Dec/12

Status: Resolved
Project: Couchbase PHP client library
Component/s: None
Affects Version/s: 1.1.0
Fix Version/s: 1.1.0
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Matt Ingenthron Assignee: Trond Norbye
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Mac OS 10.8
2.0 build 1971

Attachments: File packetdump-PCBC-159.pcapng     File packetdump-PCBC-159_second-time.pcapng     Text File php_test_results_20121205_0327.txt     Text File php_test_results_20121205_0339.txt     Text File php_test_results_20121205_0623.txt     Text File php_test_results_20121205_0637.txt    

When running the tests with the build mentioned above, I relatively regularly receive timeouts during the sync tests. Given that the host is localhost and there is no active workload (and it's on ssd), these seem to indicate a problem with the implementation of the required-durability functions.

Comment by Matt Ingenthron [ 05/Dec/12 ]
logs showing the timeout exceptions. these don't have much data, but maybe there's something interesting?
Comment by Mark Nunberg [ 05/Dec/12 ]
I've seen this issue as well (but initially thought I was just having a slow cluster). I'm willing to bet the issue is in the timeout loop itself rather than in libcouchbase or in somewhere 'deeper', as the other Observe tests pass.

Additionally, they seem to take very long to complete (patch below does not).

What's odd is that I've run this through valgrind and it didn't show any particular errors, and the errors are not always reproducible.

fwiw, this seems to pass the tests

Comment by Matt Ingenthron [ 05/Dec/12 ]
Attached a packet capture showing the same issues. I'm going to reconfigure the server and see if they go away, because I clearly see the polling, but I've not looked to see what's happening with the poll.
Comment by Matt Ingenthron [ 05/Dec/12 ]
Have a different failure under the remove scenario here. This isn't a timeout.

Comment by Trond Norbye [ 05/Dec/12 ]
Generated at Sun Jul 13 03:39:20 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.