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:
Why is 1605 there twice?
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
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:
Why is 1605 there twice?