Hi Team,
Environment - Clustered environment deployed in multiple namespaces using K8s/AWS EKS. AWS EBS volumes are used as Content Repositories. AWS EBS being bounded resources, one doesn't get to implement elasticity to its fullest. Could you please suggest ways/recommend reference materials to follow in order to make one such NiFi clustered setup fully elastic as far as it's content repository is concerned. With current setup, the disc runs out of space. Using some of the config properties like - nifi.content.claim.max.appendable.size nifi.content.repository.archive.backpressure.percentage etc. This can be controlled in a certain way by applying back pressure. Is there any other way around this to make it fully elastic on AWS depending on the input data size. -- Warm Regards, *Ketan Kankapure*
