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

Test for sqlite corruption and dataloss #118

Open
markstory opened this issue Jan 15, 2025 · 0 comments
Open

Test for sqlite corruption and dataloss #118

markstory opened this issue Jan 15, 2025 · 0 comments

Comments

@markstory
Copy link
Member

markstory commented Jan 15, 2025

Within the GCP sandbox attempt to cause SQLite corruption or database loss. We're not confident in how stateful sets will preserve sqlite across restarts and scale operations. Attempt the following:

  • restarting brokers
  • pod moves, have k8s reschedule pods on new nodes.
  • force taskbroker to panic!
  • force taskbroker to oom

Ideally these scenarios do not result in the loss of a sqlite database.

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

No branches or pull requests

1 participant