Re: Setting zookeeper.sasl.client=false

t=false, would your NiFi cluster fail to read its > own Z-Nodes on next restart? > > I've been wanting to try this for a while, but haven't had time. > > -Bryan > > On Fri, Aug 2, 2019 at 3:09 PM Chad Woodhead wrote: >> >> I’m building a flow that uses ExecuteSQL to

Setting zookeeper.sasl.client=false

I’m building a flow that uses ExecuteSQL to query data from Phoenix on top of a Kerberized Ambari Metrics’ HBase (it hits the AMS Zookeeper). I ran into issues and the logs showed NiFi (also kerberized) was getting auth failed when connecting to ZNode. To confirm I had all my proper AMS conf

Re: Problems with NiFi Registry Conflicts after Processor Upgrades

Hey guys, I'm going to be upgrading my NiFi clusters to 1.9.1 soon so this topic was important to me. I've done some testing and wanted to share my results. *Test environment setup*: 2 NiFi Clusters 1 NiFi Registry Dev NiFi on 1.8.0 versioning flows with NiFi Registry 0.2.0 Cert NiFi on 1.8.0

Re: Different NiFi Node sizes within same cluster

t;> >> > > > >> >> My "solution" was to move everything to new hardware which we > had inbound anyway. > > > >> >> > > > >> >> On Wed, 6 Mar 2019, 20:40 Jon Logan, > wrote: > > > >> >>> > &g

Different NiFi Node sizes within same cluster

Are there any negative effects of having filesystem mounts (dedicated mounts for each repo) used by the different NiFi repositories differ in size on NiFi nodes within the same cluster? For instance, if some nodes have a content_repo mount of 130 GB and other nodes have a content_repo mount of 125

Re: Versioned flows not maintaining Load Balance Strategy

and pulled 0.2.0 but kept the label 0.3.0. So I'm actually running 0.2.0 and this explains the behavior I'm seeing. Thanks for the help and hopefully this helps anyone use running HDF and seeing this behavior. -Chad On Tue, Feb 19, 2019 at 4:02 PM Chad Woodhead wrote: > Bryan, > &g

Re: Versioned flows not maintaining Load Balance Strategy

> vendor distribution. > > As far as I can tell, it is working correctly on apache releases of > NiFi 1.8.0/1.9.0-RC2 and registry 0.3.0. > > -Bryan > > On Tue, Feb 19, 2019 at 3:27 PM Chad Woodhead > wrote: > > > > Bryan, > > > > I also just tested

Re: Versioned flows not maintaining Load Balance Strategy

Bryan, I also just tested with a new flow not in version control with NiFi Registry and then started version control with it, and same behavior on my side. No load balance connection properties in the snapshot. Thanks, Chad On Tue, Feb 19, 2019 at 3:21 PM Chad Woodhead wrote: > Br

Re: Versioned flows not maintaining Load Balance Strategy

a1b818e-1d2e-3c42-a956-1796392e85be", > "labelIndex" : 1, > "loadBalanceCompression" : "DO_NOT_COMPRESS", > "loadBalanceStrategy" : "ROUND_ROBIN", > > If using the file based storage then the paths in flow_storage are >

Versioned flows not maintaining Load Balance Strategy

I am running NiFi 1.8.0 and NiFi Registry 0.3.0. I have noticed load balance strategies on queues aren't coming through versioned flows in NiFi Registry. Here are the steps I am performing: 1. Have existing flow running on latest flow version in Dev and Cert (flow has already been developed and

Re: Automate NiFi Ranger Policies

org/apidocs/index.html > [3] https://pypi.org/project/nipyapi/ > [4] https://github.com/Chaffelson/nipyapi > [5] https://ranger.apache.org/apidocs/ui/swagger.json > [6] https://ranger.apache.org/apidocs/ui/index.html > [7] https://swagger.io/tools/swagger-codegen/ > > Hope this

Automate NiFi Ranger Policies

We use Ranger with NiFi for security and we are looking to automate the creation of our Ranger policies. The way we organize our flows is like this: NiFi Root Canvas > Ingest Channel PG > Application PG We create 3 Ranger Policies per Application PG: -/process-groups/ -/data/process-groups/

Re: Failed to read TOC File

ou can go back and look at it for debugging purposes, etc. > > These are probably the most critical things, in terms of performance and > utilization. > > Thanks > -Mark > > > On Feb 13, 2019, at 2:31 PM, Chad Woodhead wrote: > > Mark, > > That must be it! I have

Re: Failed to read TOC File

> temporarily before shrinking back down, you'll want to give it a little > bit of wiggle room. > > Thanks > -Mark > > > On Feb 13, 2019, at 1:31 PM, Chad Woodhead wrote: > > Hey Joe, > > Yes nifi.provenance.repository.implementation= > org.apach

Failed to read TOC File

I use the org.apache.nifi.provenance.WriteAheadProvenanceRepository and I am seeing the following error in my logs a lot and I can't view any provenance data in the UI: 2019-02-13 12:57:44,637 ERROR [Compress Provenance Logs-1-thread-1] o.a.n.p.s.EventFileCompressor Failed to read TOC File

Re: AmbariReportingTask help

relates > to any RECEIVE or FETCH provenance events. > > If you go to the Summary table (menu in the top right / Summary) and then go > to the > Process Groups tab, you can see the Sent/Received metrics over the past 5 > minutes there. > > Thanks > -Mark > > >&

AmbariReportingTask help

I was looking for some clarification on the AmbariReportingTask, and specifically the metrics FlowFilesReceivedLast5Minutes and BytesReceivedLast5Minutes. Looking at the configuration for AmbariReportingTask, it has the property ‘Process Group ID’ and explains that if left blank, the root

Re: process group name reverts back to initial value if I do a nifi registry "Change version"

Bryan/Josef, Just wanted to let you know that I just tested this with NiFi 1.8.0 and NiFi Registry 0.3.0 and I experience the same behavior as Josef. -Chad > On Jan 8, 2019, at 12:58 PM, Bryan Bende wrote: > > I will keep trying, but I haven't been able to reproduce using NiFi > 1.8.0 and

Re: Cron-schedule not working

seems like nifi cron expressions are quite different. > > >> On Tue, Jan 1, 2019 at 11:58 AM Asanka Sanjaya wrote: >> Thanks Chad! >> >>> On Mon, Dec 31, 2018 at 6:22 PM Chad Woodhead >>> wrote: >>> Hi Asanka, >>> >>> The cron ex

Re: Cron-schedule not working

Hi Asanka, The cron expression for every night at midnight is: 0 0 * * * 0 0 0 * * is not a valid cron expression as the 3rd field (day of month) cannot be a 0. Here is an online cron editor that can help build your cron expressions: https://crontab.guru/ Also here