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.

Sign up for GitHub

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

Jump to bottom

Hypothesis: We can handle storage errors #9

Open
ChrisKujawa opened this issue Mar 4, 2020 · 0 comments
Open

Hypothesis: We can handle storage errors #9

ChrisKujawa opened this issue Mar 4, 2020 · 0 comments
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Low The issue is really unlikely.

Comments

@ChrisKujawa
Copy link
Member

Hypothesis

We believe that we are able to handle IO errors/ storage errors
@ChrisKujawa ChrisKujawa added Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Low The issue is really unlikely. Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. labels Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Contribution: Availability This issue will contribute to build up confidence in reliability. Contribution: Reliability This issue will contribute to build up confidence in reliability. Hypothesis A thing which worries us and is ready for exploration. Impact: High The issue has an high impact on the system. Likelihood: Low The issue is really unlikely.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ChrisKujawa