[Bug]: Delayed traces on fetching from Elasticsearch

[TheOxFromOutOfTheBox]

What happened?

I have some traces having around 7000 spans each.
I'm running some jobs generating a total of 5-6 traces.
They've been posted to Elasticsearch already, I've queried and verified.
However they are not visible on Jaeger UI for a while and then they come slowly after a gap.

Attaching screenshot below, the name of the trace contains the timestamp it was run but there is a larger gap in the time they were recieved.

I suspected a network issue but I'm running everything on the same machine, and the problem persists

Steps to reproduce

1. create traces
2. store in elasticsearch and verify.
3. check in jaeger ui

Expected behavior

all traces should appear in the ui without noticeable delay from execution time

Relevant log output

No response

Screenshot

No response

Additional context

No response

Jaeger backend version

v1.47

SDK

OpenTelemetry C++ SDK

Pipeline

OTEL SDK -> OTEL Collector -> Jaeger All in One -> Elasticsearch

Stogage backend

Elasticsearch v7.17.10

Operating system

Linux

Deployment model

Docker

Deployment configs

No response