You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 3.8 we include tracing for the transport along with requests, for collocated calls we could include "collocated = true" to make clear that the transport info is not present because the requests is a collocated request.
See for example this tracing:
-- 12/12/24 18:11:30385 ./writer: Protocol: sending request
message type = 0 (request)
compression status = 0 (not compressed; do not compress response, if any)
message size = 159
request id = 1
identity = forwarders/2
facet =
operation = announceTopicWriter
mode = 2 (idempotent)
context =
encoding = 1.1
....
-- 12/12/24 18:11:30386 ./writer: Protocol: sending request
message type = 0 (request)
compression status = 0 (not compressed; do not compress response, if any)
message size = 163
request id = 0 (oneway)
identity = DataStorm/Lookup
facet =
operation = announceTopicWriter
mode = 2 (idempotent)
context =
encoding = 1.1
transport = udp
local address = 192.168.86.184:59947
remote address = 239.255.0.1:10000
The initial announceTopicWriter send to forwarders/2 is a collocated requests, that is why it doesn't include any transport info. Adding collocated = true would make clear it is a collocated request.
The text was updated successfully, but these errors were encountered:
In 3.8 we include tracing for the transport along with requests, for collocated calls we could include "collocated = true" to make clear that the transport info is not present because the requests is a collocated request.
See for example this tracing:
The initial
announceTopicWriter
send toforwarders/2
is a collocated requests, that is why it doesn't include any transport info. Addingcollocated = true
would make clear it is a collocated request.The text was updated successfully, but these errors were encountered: