DomGarguilo commented on PR #5398: URL: https://github.com/apache/accumulo/pull/5398#issuecomment-2776913307
Okay I stood up an instance via uno using this branch and configured and enabled tracing. In Jaeger, I see the traces which from what I can tell, indicate that things are working properly here. I started the shell, turned on tracing, created a table, ingested an entry to that table, scanned the table then turned tracing off. Here is what im thinking based on what i see in jaeger. Please correct me if anything seems wrong: ## Protocol and header * I did not see any validation errors * I saw evidence of cross-process communication (in this case spans from shell process to manager to tserver) * I see "AccumuloProtocol::" spans followed by handler spans in another process ## client/server protocol distinction * It seems like the code thats in place to add the header if its a client and read the header if its a server is working. I see accumulo components functioning as both "clients" (when sending) and "servers" (when receiving). The tags associated with the spans indicate if its a "client" or "internal" span and i see the components acting as both which indicates that the logic that adds and verifies the headers is probably working. ## Trace context propagation * I see a single trace ID across all processes from shell -> manager -> tserver spans -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@accumulo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
