[Bug]: Max clock skew setting not applied in v2

[dnaka91]

What happened?

I'm having a distributed tracing setup in which some devices have a clock difference of several seconds and wanted to adjust the maximum clock skew adjustment duration.

After some digging into the config structures, I found that the yaml setting should be as follows and confirmed it's parsed and accepted by the server, as it errors on any unknown config field:

extensions:
  jaeger_query:
    max_clock_skew_adjust: 5s

This is the equivalent of the --query.max-clock-skew-adjustment=5s of Jaeger v1.

However, it seems this setting is not being applied in v2 at all, as regardless of what duration is set, it always applies the default of 1 second.

Steps to reproduce

1. Have a Jaeger instance and two OTLP clients set up with different clock timing.
   1.1. The clients should have a clock difference of at least a few seconds.
   1.2. The clients must be setup for distributed tracing so their traces are combined in Jaeger.
2. Configure Jaeger to accept larger durations that 1 second.
3. View a trace in the UI that is a distributed trace of both clients.
4. Verify that the spans of the clients are far apart and not normalized, despite the configured max clock skew adjustment. A warning will be shown in the spans, saying that the clock skew exceeds the limit.

Expected behavior

The Jaeger server should apply the max clock skew adjustment setting accordingly.

Relevant log output

Screenshot

No response

Additional context

No response

Jaeger backend version

v2.2.0

SDK

Rust setup with tracing, tracing-subscriber, tracing-opentelemetry and various crates from the opentelemetry-rust project.

All with the latest version as of writing, but this appears to be no client-side error anyway.

Pipeline

OTEL SDK -> [OTLP] -> Jaeger v2

Same pipeline for 2 clients, but the clients are on different installments:

• Server system receiving requests.
• Android app sending requests.

In a local setup the server is run in Docker, and the app is run in an Android emulator.

Stogage backend

Badger

Operating system

Linux

Deployment model

Docker Compose

Deployment configs

[dnaka91]

I already have a draft PR for this and just opened it, which should fix the problem but I haven't had a chance to properly test it yet.

Also, there is an open question from my side for the default setting of 1 second.