Updates scheduler docs with latest changes on needed storage #4303
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Elena Kolevska <[email protected]>
artursouza
suggested changes
Aug 9, 2024
| By default, the Scheduler service database writes this data to an in-memory ephemeral tempfs volume, meaning that **this data is not persisted across restarts**. Job data will be lost during these events. | ||
|
|
||
| To make the Scheduler data resilient to restarts, a persistent volume must be mounted to the Scheduler `StatefulSet`. | ||
| The [Scheduler]({{< ref scheduler.md >}}) service is responsible for writing jobs to its embedded database and scheduling them for execution. On installation, a Persistent Volume Claim (PVC) is automatically created on the default storage class, providing durable storage for the Scheduler database and making it resilient to restarts or cluster failure. |
There was a problem hiding this comment.
Please, mention somewhere that the default size is 1Gi and it can be changed. It is recommended to use 10Gi for production.
There was a problem hiding this comment.
Currently, the docs suggest 64GB, should we update that, or leave it as is?
Signed-off-by: Elena Kolevska <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Default installations will always try to create a PVC, no matter the value of the ha flag, nor the storageClass flag.