Skip to content

Conversation

siying
Copy link
Contributor

@siying siying commented Jun 30, 2021

Summary:
Previously Stress can inject metadata write failures when reopening a DB. We extend it to file append too, in the same way.

Test Plan: manually run crash test with various setting and make sure the failures are triggered as expected.

Summary:
Previously Stress can inject metadata write failures when reopening a DB. We extend it to file append too, in the same way.

Test Plan: manually run crash test with various setting and make sure the failures are triggered as expected.
@siying siying force-pushed the stress_open_write_error branch from 49a7a9a to f549eda Compare June 30, 2021 22:11
@facebook-github-bot
Copy link
Contributor

@siying has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Copy link
Contributor

@zhichao-cao zhichao-cao left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in ba224b7.

facebook-github-bot pushed a commit that referenced this pull request Jul 6, 2021
)

Summary:
Write and metadata error injection during DB open was enabled in #8474. This causes crash tests to fail very frequently due to another fault injection feature that deletes files created after the last dir sync during DB open. In real life, a similar failure would happen if the FS returns error on the CURRENT file rename, but the rename actually succeeded and got partially persisted (dir entry for the old CURRENT file got removed, but the entry for the new one is not persisted). Temporarily disable the fault injection feature until we figure out the likelihood of this bug happening and the proper way to fix it.

Pull Request resolved: #8489

Test Plan: Stress test can open the DB successfully

Reviewed By: siying

Differential Revision: D29564516

Pulled By: anand1976

fbshipit-source-id: ffd1650715ea3c5bf7131936b0ca6fcf66f4e14e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants