Details
-
Task
-
Resolution: Fixed
-
Major
-
3.1.4
-
None
-
None
-
1
Description
When intentionally putting a system into a scenario where a cluster node fails, the client will expectedly log timeouts. I think it's also expected that it logs it with the instance identifier and the operation ID per RTO, but it looks like it's just showing the operation ID twice.
The message from the exception is:
Failed during upsert: The operation 1605/1605 timed out after 00:00:02.5000000. It was retried 1 times using Couchbase.Core.Retry.BestEffortRetryStrategy.
|
Why is 1605 there twice?