ownloaded the latest JRE, but still get the same
>> error message.
>>
>>
>>
>>
>>
>> *From:* Swarup Karavadi
>> *Sent:* Monday, October 21, 2019 12:19 PM
>> *To:* users@nifi.apache.org
>> *Cc:* jgres...@gmail.com
>> *Subject:* Re: NiFi
If you are hosting on the cloud, I'd recommend going for dedicated worker
nodes for the NiFi cluster. There might be rare (or not) occasions when a
worker node is under high load and needs to evict pods. If your NiFi
deployment's pod disruption budget allows for eviction of pods then there
are
nment/situation that is
>> causing the ServletContext and ApplicationContext to get
>> configured/initialized differently. This could be something specific
>> to your environment or it could be uncovering an edge-case bug in
>> NiFi.
>>
>> I think o
Greetings,
I have deployed a single node unsecured NiFi cluster (I say cluster because
nifi.cluster.is.node is set to "true") as a stateful set on Kubernetes (AWS EKS
to be specific). The NiFi cluster sits behind an Nginx ingress. I have
configured the Nginx ingress to forward the appropriate
