jaeger search result is unusual

[molon]

According the gif upon.
We can see the trace time of results change often.
So the result would lose some traces sometimes.
But We want to see the nearest traces timely.
And I ensure that there is no more trace produce (beacuse this is just a test env).

I think it's strange~

[black-adder]

How are you running jaeger? Are you running all-in-one? Running the services separately using cassandra/es?

[lapointexavier]

I observed that running the all-in-one ✋ Is it expected since it's meant to be more of a temporary / development solution?

[black-adder]

Looks related to: jaegertracing/jaeger-ui#57

@molon if you increase the "Limit Results" to something like 1000 and repeat this, do you see the same thing happening?

[molon]

@black-adder Thanks for reply.

jaegertracing/jaeger-ui#57

I see - the memstore implementation likely doesn't provide stable search, because it uses hash maps internally. It's doable, but doesn't seem too important.

This is the problem. :)