Hi Saulo, Might you be able to specify the version you are using? If possible, could you also share your config.yml?
The second point is expected behavior as the config file is transformed into nifi.properties. However, the items you are trying to adjust are not enabled as archiving is disabled by default in MiNiFi instances. It would seem that there are either FlowFiles not being transferred out of the flow (they are never terminated at a processor) or there is a bug in the content repository itself. Any information about environment/OS you can provide would help in troubleshooting. Thanks! --aldrin On Tue, Jan 16, 2018 at 5:01 AM, Saulo <[email protected]> wrote: > Hi all, > > > I started using NiFi and MiNiFi just a few days ago. For my first MiNiFi > setupI have deployed a simple flow that tails some log files in a folder > and > then emits the results to NiFi. > > Now I found 2 problems in this setup. > > - The first is related to my MiNiFi ./content_repository. This path is > using > around 120GB of disk space, which is far more than I can afford for this > application; > > - The second is related to the solution I tried to the previous problem. I > tried to configure the MiNiFi nifi.properties with the following values: > ´´´ > nifi.content.repository.archive.max.retention.period=6 hours > nifi.content.repository.archive.max.usage.percentage=5% > ´´´ > > However, when I restart MiNiFi this instance for it to use the new > properties, I noticed that it overwrites my nifi.properties file with some > default values erasing the new values. > > > > Am I doing something wrong? How should I do to configure MiNiFi with the > new > properties? > > > > Thank you very much for the help in advance. > > > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/ >
