Invokehttp errors process first before original message

Hi all, I have a scenario here, Messages are flowing sequentially into an invoke HTTP processor. Let's say the first few messages fail and went to the failure state. Is there any way that I can rerun the errored message first then execute the rest of the message in the order. If so please let me

Re: 1.11.3 trust store error

You can post them on a temporary file sharing service, post them in the Apache NiFi Slack [1], or email them to me directly at alopre...@apache.org . The mailing list software tends to strip attachments. [1] https://apachenifi.slack.com

Re: 1.11.3 trust store error

Good question -- I can't share these keystores and truststores, but I'll see if I can generate some test ones tomorrow. How should I send them to you? On Wed, Feb 26, 2020 at 8:01 PM Andy LoPresto wrote: > Joe, > > Can you share the keystores and truststores you are using? I understand > the

Re: 1.11.3 trust store error

Joe, Can you share the keystores and truststores you are using? I understand the issue you’re encountering but we haven’t yet been able to reproduce it locally running with certs that work on 1.11.1. Please DO NOT share actual keystores if they contain real private keys, only if these are dev

Re: 1.11.3 trust store error

Ok, I added all the server certs and my administrator's client cert to the trust store, and they all still got PKIX path building failed. So I redeployed nifi 1.11.1, and now it works again. Joe On Wed, Feb 26, 2020 at 6:21 PM Joe Gresock wrote: > Yes, on Kubernetes. > > FWIW, I do see

Re: 1.11.3 trust store error

Yes, on Kubernetes. FWIW, I do see changes to nifi-commons/nifi-security-utils/src/main/java/org/apache/nifi/security/util/SslContextFactory.java involving a new function createTrustSslContextWithTrustManagers(), among other related changes. I'm going to try directly adding the client certs to

[ANNOUNCE] Apache NiFi 1.11.3 release

Hello The Apache NiFi team would like to announce the release of Apache NiFi 1.11.3. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs of data routing, transformation,

Re: 1.11.3 trust store error

on kubernetes is a key detail here too... On Wed, Feb 26, 2020 at 10:01 AM Joe Gresock wrote: > Java 8 > > On Wed, Feb 26, 2020 at 5:59 PM Nathan Gough wrote: > > > Hi Joe, > > > > I just set up a secure cluster with NiFi 1.11.3 and am not seeing any > > issues like you describe. > > > > Are

Re: 1.11.3 trust store error

Java 8 On Wed, Feb 26, 2020 at 5:59 PM Nathan Gough wrote: > Hi Joe, > > I just set up a secure cluster with NiFi 1.11.3 and am not seeing any > issues like you describe. > > Are you running Java 8 or Java 11? > > Nathan > > On Wed, Feb 26, 2020 at 12:22 PM Joe Gresock wrote: > > > Were there

Re: 1.11.3 trust store error

Hi Joe, I just set up a secure cluster with NiFi 1.11.3 and am not seeing any issues like you describe. Are you running Java 8 or Java 11? Nathan On Wed, Feb 26, 2020 at 12:22 PM Joe Gresock wrote: > Were there any changes with how the trust store is used in 1.11.3? I had a > 1.11.0

1.11.3 trust store error

Were there any changes with how the trust store is used in 1.11.3? I had a 1.11.0 deployment working with the following settings, but when I deployed 1.11.3, the cluster can't seem to replicate requests to itself: nifi.remote.input.host= nifi.remote.input.secure=true

Re: [DISCUSS] On HBase client retries (NIFI-6197)

I'm not sure either. I agree that 35 is too high, the 2.x++ default of 15 seems reasonable to me. We might be able to include a connection check API in the future but that won't help us now so we need to find some way forward. I believe we have different "services" in NiFi for HBase 1 & 2. How