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

WT-3603 format threads always traverse the same RNG space. #3672

Merged
merged 6 commits into from Sep 26, 2017

Conversation

keithbostic
Copy link
Contributor

While looking at one of the WT-3435/#3644 failures, I realized all of the format threads were pounding on the same key/value pairs. Interestingly enough, if you change that, the failure goes away.

I think we generally want the format threads to work different parts of the RNG space, but clearly we also want to stress the same key/value pairs as well.

Initialize the format threads to run in different parts of the RNG space
70% of the time.
@keithbostic keithbostic self-assigned this Sep 24, 2017
@agorrod
Copy link
Member

agorrod commented Sep 25, 2017

Thanks @keithbostic lgtm

@agorrod
Copy link
Member

agorrod commented Sep 25, 2017

Actually @keithbostic I was on the verge of merging this, but then thought the option may be critical for reproducing failures - do you think it should be exposed via the configuration file?

@keithbostic
Copy link
Contributor Author

I was on the verge of merging this, but then thought the option may be critical for reproducing failures - do you think it should be exposed via the configuration file?

I think that's a good point (and it's not like configuration variables are expensive to add).

I've pushed that change for your consideration.

@agorrod
Copy link
Member

agorrod commented Sep 26, 2017

Thanks @keithbostic lgtm

@agorrod agorrod merged commit d3edf05 into develop Sep 26, 2017
@agorrod agorrod deleted the wt-3603-format-rng-space branch September 26, 2017 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants