On Tue, 2 Feb 2021, 01:18 jgunvaldson, <mailto:jgunvald...@cox.net>> wrote:
> Wiring up a rest client to make a rest request to the NIFI API, seems the
> following three are possible candidates:
>
> GET /controller-services/{id} Gets a controller
>
ote:
>
> John,
>
> You're using a vendor distribution of NiFi. You should contact the vendor.
>
> You can certainly monitor the state of a controller service via the REST API.
> They should either be enabled or not enabled.
>
> Thanks
>
> On Mon, Feb 1, 2021 at 5
Hi All,
Root level (canvas) Controller Services - We tend to setup several Root level
Controller services for developers that are typically DBCPConnectionPools and
DistributedMapCacheClientService and maybe a few other. MOST importantly, these
controller services cannot be down and cannot be
I passed this along to the primary developers - Thanks Mike!
Best Regards
John
> On Dec 3, 2020, at 1:11 PM, Mike Thomsen wrote:
>
> One of my colleagues ran into a similar situation, and all that was
> required to fix it was to make ReplaceText work line by line. When you
> do that, you
Thanks Joe,
I am getting the general opinion that on OOM restart is not optional, must be
done. In that case I am going to also look at some of the following
-XX:+ExitOnOutOfMemoryError
-XX:+CrashOnOutOfMemoryError
ExitOnOutOfMemoryError
When you enable this option, the JVM exits on the first
Just looking for an opinion
Knowing (for one example) that ReplaceText Processor can be very memory
intensive with large files - we are finding it more and more common to wake up
to an Out of Memory error like the following
2020-12-03 15:07:21,748ZUTC ERROR [Timer-Driven Process Thread-31]
020, at 10:34 AM, jgunvaldson wrote:
>
> Powered by Apache NiFi Version 1.9.0
> 1.9.0.3.4.1.1-4 built 05/01/2019 02:15:30 UTC
> Tagged nifi-1.9.0-RC2
> 6 Node Cluster
>
> ~~
>
> This is a long shot, but I have developers reporting an inability to disable
> a “AvroS
Powered by Apache NiFi Version 1.9.0
1.9.0.3.4.1.1-4 built 05/01/2019 02:15:30 UTC
Tagged nifi-1.9.0-RC2
6 Node Cluster
~~
This is a long shot, but I have developers reporting an inability to disable a
“AvroSchemaRegistry” controller service without a couple of the Cluster nodes
disconnecting
g up the
> Controller Service by name.
>
> Hope this helps!
> -Mark
>
>
>> On Sep 8, 2020, at 12:59 PM, jgunvaldson > <mailto:jgunvald...@cox.net>> wrote:
>>
>> We are working through various alternatives for migration of flows from our
>> ol
We are working through various alternatives for migration of flows from our old
DEV environment to other (new DEV, QA and PROD)
Currently the approach we use invalidates all processors that use controller
services established on root and domain flow level (import of FLOW does not
duplicate
I think that is part of the problem, and probably part of the solution.
If I can wire load balancer to do a HTTP HEAD (a property of the
HandleHttpRequest) - knowing that this is a “Separate” Jetty instance means I
should get a 200 from the HEAD
Something like that
> On Sep 4, 2020, at
ng like http(s)://server/ping
> And the response is just pong
>
>
>
> Le ven. 4 sept. 2020 à 18:02, jgunvaldson <mailto:jgunvald...@cox.net>> a écrit :
> Hi,
>
> Our network administrators are unable to wire up advanced Load Balancer (AWS
> Application Load
Hi,
Our network administrators are unable to wire up advanced Load Balancer (AWS
Application Load Balancer) or (Apache reverse proxy) to leverage a NIFI API
that may be listening on a port across several nodes.
For instance, a HandleHttpRequest listing on Node-1 on PORT 5112, Node-2 on
5112,
Hi All,
We use a API Manager from WSO2 to proxy our NIFI APIs. This provides
subscription, OAUTH and other features that are very useful
Problem is when a node is disconnected in NIFI (don’t ask, happens more than we
would like) then our API Manager, having been configured to use that node -
Just FYI, I found the answer
https://community.cloudera.com/t5/Support-Questions/NiFi-Toolkit-Can-t-start-NiFi-with-a-75MB-gzipped-flow-xml/td-p/288712
Exact same problem with proper solution
Fixed…
> On Aug 21, 2020, at 3:48 PM, jgunvaldson wrote:
>
> We have a production instanc
We have a production instance of NIFI (1.9.0.3.4.1.1-4 built 05/01/2019
02:15:30 UTC Tagged nifi-1.9.0-RC2) with an unusual symptom.
We know, that on a new instance of NIFI, the canvas comes up empty (result of a
new flow.xml). Developers then start building process
groups and more from this
16 matches
Mail list logo
