Mike, would setting a limit on disk utilization meet your business requirements? I believe that functionality already exists. It’s been a while since I messed with it, but we’ve used it to ensure we didn’t up all the (relatively paltry) disk on a test VM. I know it works because we DID run out of disk once prior to configuring the appropriate settings.
Caterpillar: Confidential Green From: Bryan Bende <[email protected]> Date: Wednesday, August 14, 2024 at 10:58 To: [email protected] <[email protected]> Subject: Re: Get system configuration from a processor CAUTION: EXTERNAL EMAIL This is a message from [email protected]. Use caution when opening unexpected emails and do not click on links or attachments from unknown senders. For more resources, visit security.cat.com/phishing. ______________________________________________________________________ There is a NiFiProperties object, but it is only meant to be used by the framework and framework extensions, not extensions like processors and controller services. Those get their config from their properties, or from things specifically given to them through the defined extension API. On Wed, Aug 14, 2024 at 11:44 AM Phillip Lord <[email protected]> wrote: > > Perhaps you already know this, but... > > You can monitor free space in cont-repo through the UI. > > If you have a cluster go to the global menu -> Cluster -> Content Storage > Stand-alone go to global menu -> Summary -> system diagnostics -> System > > I suppose if you wanted to you could Pull the > https://urldefense.com/v3/__http://nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$<https://urldefense.com/v3/__http:/nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$> > file > periodically w/ a getFile (set "keep source file" to "true"), and you could > evaluate the > https://urldefense.com/v3/__http://nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$<https://urldefense.com/v3/__http:/nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$> > that way? Although a little odd... but it > could be done nonetheless :) > On Aug 14, 2024 at 11:26 AM -0400, Mike Thomsen <[email protected]>, > wrote: > > I can open the > https://urldefense.com/v3/__http://nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$<https://urldefense.com/v3/__http:/nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$> > file manually. I was just wondering if there > was a singleton object or something that held its values somewhere. > > On Wed, Aug 14, 2024 at 11:25 AM Mike Thomsen <[email protected]> > wrote: > > The location info for the content repositories so I can monitor the free > space. > > Our use case is a bit of a weird one driven by us having to hack around > budget issues that aren't aligned with the expectations on the raw volume > and size of the data these nodes will handle. > > On Tue, Aug 13, 2024 at 8:20 AM Bryan Bende <[email protected]> wrote: > > Processors should not know about > https://urldefense.com/v3/__http://nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$<https://urldefense.com/v3/__http:/nifi.properties__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-G6RkUEa$> > . > > What information are you trying to get? > > On Tue, Aug 13, 2024 at 7:52 AM Mike Thomsen <[email protected]> > wrote: > > Is there a 1.X and 2.X safe way to get the configuration data from > https://urldefense.com/v3/__http://nifi.properties?__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-K9VpmZs$<https://urldefense.com/v3/__http:/nifi.properties?__;!!FtR4BK4x7WL3xYs!4Ryl6r9JPWn3nKsxsyEQ1yBYsLexaUUHGry9wpztXkn8gZa5FJjGze2VkTXoJswbyNa7-K9VpmZs$> > > Thanks, > > Mike
