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

Create a "restart during load" test for Storage #494

Open
SandGrainOne opened this issue Sep 13, 2024 · 0 comments
Open

Create a "restart during load" test for Storage #494

SandGrainOne opened this issue Sep 13, 2024 · 0 comments
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Sep 13, 2024

Description

We need to have a better understanding of what time Storage needs when performing shutdown and startup. We need to adjust the probe settings used by k8 during operations like a deploy.

The method to use is to perform restarts during load.

Initial ideas for a test:

  • Create one or more instances of an app.
  • Distribute 50+ data blobs of at least 10 Mb in size among the instances.
  • Prepare a test script to download blobs with a configurable number in parallell.
  • Run tests where Storage is resarted and look for errors.
  • Make adjustments to probes and try again

Additional Information

No response

Tasks

No response

Acceptance Criterias

No response

@SandGrainOne SandGrainOne added kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Sep 13, 2024
@SandGrainOne SandGrainOne changed the title Create a restart during load test for Storage Create a "restart during load" test for Storage Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

1 participant