简体繁体 English

Jaeger 跟踪无序

[英]Jaeger traces out of order

原文 2022-10-03 23:04:40 6 1 javascript/ java/ microservices/ jaeger/ opentracing

I have a front-end application (component A) that makes a request to a Java back-end application (component B).我有一个前端应用程序（组件 A）向 Java 后端应用程序（组件 B）发出请求。

Both components are configured to export trace information to my jaegertracing/all-in-one:1.37 deployment.这两个组件都配置为将跟踪信息导出到我的 jaegertracing/all-in-one:1.37 部署。

The headers from component A are propagating correctly to component B, and I can see the traces being nested, but they are out of order.组件 A 的标头正确传播到组件 B，我可以看到嵌套的跟踪，但它们是乱序的。

I printed the start and end time for both component A and B, it looks like timestamp from component B is earlier than of component A. Has anyone run into this issue before?我打印了组件 A 和 B 的开始和结束时间，看起来组件 B 的时间戳比组件 A早。以前有人遇到过这个问题吗？

The way I print the epoch time for both services are:我为这两种服务打印纪元时间的方式是：

Java System.currentTimeMillis(); Java System.currentTimeMillis();

JavaScript new Date().getTime() JavaScript新日期().getTime()

1 个解决方案

Jaeger has a solution to address the possibility of clock skew between the many host machines part of the traces: https://www.jaegertracing.io/docs/1.21/deployment/#clock-skew-adjustment Jaeger 有一个解决方案来解决跟踪的许多主机部分之间时钟偏差的可能性： https://www.jaegertracing.io/docs/1.21/deployment/#clock-skew-adjustment

It is most likely the case that one of the host machines have a clock skew which causes the tracing to be out of order.最有可能的情况是其中一台主机有时钟偏差，导致跟踪无序。