Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.2.0
-
None
-
None
-
1
Description
I tested the latest master and got an output for KV of like:
{
|
"total_duration_us":224,
|
"encode_duration_us":36,
|
"last_dispatch_duration_us":134,
|
"total_dispatch_duration_us":134,
|
"operation_name":"get",
|
"last_local_id":"2",
|
"operation_id":"1114",
|
"last_local_socket":"127.0.0.1:11210:56020",
|
"last_remote_socket":"127.0.0.1:11210:56020",
|
"timeout_ms":"00:00:02.5000000"
|
},
|
The following things do not line up to the spec I think:
- The KV server duration is not included
- the timeout format looks way odd (a string and not a number in ms)
- local and remote socket are the same and invalid, they seem to contain both sockets in one string? (local and remote)
- the local id Seems off. see spec:
Attribute: Local ID
|
The local ID is the connection ID used when creating the connection against the cluster. Note that right now the ID is only populated for the KV service. The attribute key is “db.couchbase.local_id”.
|
|
|
KV Example: “66388CF5BFCF7522/18CC8791579B567C”.
|
In addition, I found when setting the timeout to a very low value I get output like:
{
|
"total_duration_us":87,
|
"operation_name":"get",
|
"last_local_socket":":",
|
"last_remote_socket":":",
|
"timeout_ms":null
|
}
|
I think the timeout can always be present, since it is a fixed value? and last remote and local socket should not be present at all and not just contain a ":"
Attachments
| For Gerrit Dashboard: NCBC-2928 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 158034,8 | NCBC-2928: KV Tracer Output Not Aligning with Spec | master | couchbase-net-client | Status: MERGED | +2 | +1 |