Re: Securing MiNiFi

You were right. Thanks for your help. -- Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: Securing MiNiFi

We’ll try to clean up the NiFi docs, but vendor documentation is out of our control. Glad it’s working for you now. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com He/Him PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Oct 21, 2020, at 17:46, scotty

Re: Securing MiNiFi

That was it! I didn't have nifi.remote.input.http.enabled= true. I was going off of the link below where it says "By default, it is set to true." I guess I misread it to mean that if nothing was specifically entered there then it would default to true.

PrometheusReportingTask Metrics

Is there a description of each of the metrics provided by the PrometheusReportingTask available somewhere? Thank you! -- David Ritch Principal Software Engineer WaveStrike/Analytics Capabilities Division 300 Sentinel Dr. Ste. 210 Annapolis Junction, MD 20701

Re: NiFi 1.11.4 HDFS/HBASE Processor Errors After Kerberos Ticket Expires

If there is nothing in the logs but they stop working I suspect the issue is related the default prompt for name. Update settings in bootstrap is most likely needed. Thanks On Wed, Oct 21, 2020 at 3:36 PM Peter Turcsanyi wrote: > Are there any exception stack traces in the log when the

Re: NiFi 1.11.4 HDFS/HBASE Processor Errors After Kerberos Ticket Expires

Are there any exception stack traces in the log when the processors fail / before that? On Thu, Oct 22, 2020 at 12:28 AM wrote: > Hello! > > > > We’re running into a problem with NiFi 1.11.4. > > > > Our HBASE/HDFS/Parquet processors are all configured with a master > KeytabCredentialsService

NiFi 1.11.4 HDFS/HBASE Processor Errors After Kerberos Ticket Expires

Hello! We're running into a problem with NiFi 1.11.4. Our HBASE/HDFS/Parquet processors are all configured with a master KeytabCredentialsService that is pointing to a Kerberos principal and keytab file. The environment's /etc/krb5.conf file has the line renew_lifetime = 7d commented

Re: Securing MiNiFi

I think you need to at least populate one of, if not both, nifi.remote.input.socket.port= and nifi.remote.input.http.enabled=. If there is no socket port specified, and HTTP transmission is not enabled, I don’t think S2S will work. I also don’t see any keystore or truststore configured; did

Re: Securing MiNiFi

Hi, Here's the info: # Site to Site properties nifi.remote.input.host=mydomain.com nifi.remote.input.secure=true nifi.remote.input.socket.port= nifi.remote.input.http.enabled= nifi.remote.input.http.transaction.ttl=30 sec nifi.remote.contents.cache.expiration=30 secs # web properties #

NiFi on Kubernetes

Dear All, I am trying to run standalone NiFi 1.12.1 (not cluster) on Kubernetes. I am planning to migrate my NiFi instance from VM to Kubernetes. I did container PoC on Docker and it was successfully completed. Storage side was really simple I used mount parameter for persistency required folders