Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.6.4, 4.6.5, 5.0.0, 5.1.0, 5.1.1, 5.5.0
-
Untriaged
-
Release Note
-
Unknown
Description
As a part of investigating CCBC-809, we found that some internal errors exposed to SDK.
This is what SDK client might see from the Query Service:
Failed to execute query. lcb: 59, http: 500, {
|
"requestID": "14267f43-28cd-40fa-a9c2-56c330850221",
|
"signature": {
|
"*": "*"
|
},
|
"results": [],
|
"errors": [
|
{
|
"code": 5000,
|
"msg": "write tcp 172.17.0.13:9101: broken pipe from 172.17.0.13:9101 - cause: write tcp 172.17.0.13:9101: broken pipe from 172.17.0.13:9101"
|
}
|
],
|
"status": "errors",
|
"metrics": {
|
"elapsedTime": "12.458924ms",
|
"executionTime": "12.348039ms",
|
"resultCount": 0,
|
"resultSize": 0,
|
"errorCount": 1
|
}
|
}
|
The question is: "How the SDK should react on this error?"
And if it should retry, how SDK can detect this specific case?
Currently we retry error code 5000 only if it includes substring "queryport.indexNotFound".
Attachments
Issue Links
- blocks
-
-
- Closed
-