-
Notifications
You must be signed in to change notification settings - Fork 5
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
Make repository-sizes dynamic based on pvc sizes #354
Comments
…141) ## Description Related to stackabletech/nifi-operator#354
I agree that focusing on size retention makes more sense for us since PVCs are isolated based on that anyway. I think for now it'd probably be ok to let time retention be configured through config overrides if it is actually desired by the user? |
Cross-referenced which repository types would need to be configured this way, but I think otherwise the original ticket did a pretty good job. |
I'm fine with only having size based retention but the description is still a bit too unclear for me. e.g. flow: 50%, archive: 30%, provenance: 20% ? |
Currently this is a bug as |
The
part is decided by the user. He needs to specify the pvc sizes for every repository individually |
My comments were based on a misunderstanding of the proposal. Time based retention is out of scope for now. |
Almost none of the checkboxes are ticked. Neither in the PR nor here, can you make sure that everything is done? |
Checked implementation and the boxes |
Improving some demos i noticed that my NiFi instance suddenly stopped working.
Reason is that the provenance repo run out of space. It only has 5Gi but the operator hard-codes
nifi.provenance.repository.max.storage.size=10 GB
IMHO something like the following would make sense:
DoD
The following repositories don't configure any time based retention, only size based upon the actual pvc size
Wont: Additionally users can overwrite the time based retention or the percentage based retention (out of scope for this ticket)
Details
This is the current config
This are the pvc usages
Config
The text was updated successfully, but these errors were encountered: