Closed sbernauer closed 1 year ago
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. This will require a CRD change, right? I think what you're suggesting is that the PVC size is split up between all repositories automatically or should the user select a percentage of size?
e.g. flow: 50%, archive: 30%, provenance: 20% ?
Currently this is a bug as nifi.provenance.repository.max.storage.size=10 GB
is hard-coded. The demo used a pvc size of 5Gi for provenance and bad things happened.
Each repository gets a own pvc.
No CRD change is needed IMHO. We only remove the hard-coded nifi.provenance.repository.max.storage.size=10 GB
setting and put in the actual pvc size.
The
e.g. flow: 50%, archive: 30%, provenance: 20% ?
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. I thought that the CRD snippet above is the proposed new one and didn't realize that this already exists.
Time based retention is out of scope for now. Please make sure to leave a safety buffer of at least 100MB (which means we also need to validate that a storage PVC is at least 101MB in size :)
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
[x] The following repositories don't configure any time based retention, only size based upon the actual pvc size
[x] 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