Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure different tracers in HotROD process use different RNG seeds #718

Merged
merged 1 commit into from
Feb 28, 2018

Conversation

yurishkuro
Copy link
Member

I ran into a case where trace had spans with the same IDs. The RNG is seeded with time.Now().UnixNano(), which potentially can give identical values over several calls (since the clock precision is not actually nanos).

This is a quick (hacky) workaround. A proper fix needs to be in the Jaeger client.

Signed-off-by: Yuri Shkuro ys@uber.com

…nerator seeds

Signed-off-by: Yuri Shkuro <ys@uber.com>
@coveralls
Copy link

coveralls commented Feb 28, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 7cff9c6 on dedupe-random into b61b7ec on master.

Copy link
Contributor

@black-adder black-adder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't you say you tried this but still got the same issue?

@yurishkuro
Copy link
Member Author

Yes, but maybe there was another cause. I certainly was able to reproduce same-IDs from different tracers scenario.

@yurishkuro yurishkuro merged commit 25a1c56 into master Feb 28, 2018
@ghost ghost removed the review label Feb 28, 2018
@yurishkuro yurishkuro deleted the dedupe-random branch February 28, 2018 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants