Is there a limit to the number of processors that can be put into a NiFi
flow?
I'm assuming there isn't an actual hard limit but what's likely to break as
the number of processors increases, and what's considered a large number?
We currently have a few hundred processors in our graph but it's
Good deal, thanks for getting back to me about it. I think that I may make
some changes and potentially open a PR depending on what comes of it (I'll
have to take a look at the workflow and all of that good stuff first).
Cheers,
Ryan H
On Mon, Jan 29, 2018 at 12:55 PM, Bryan Bende
Ryan,
I remember creating an issue for something that seems similar to what
you are running into:
https://issues.apache.org/jira/browse/NIFI-3642
Long story short, I believe you do need to specify a value for
nifi.web.http.host because that will be used to replicate requests
that come in to the
Hi Bryan,
Yes that makes total sense, and it is what I figured was happening. So
whatever is configured for nifi.web.http.host is where api calls will go
to, but this is also what jetty will bind to, correct? So in my case, I
would have to have the additional property mentioned in
Ryan,
I'm not that familiar with Docker and DCOS, but I think what you said
is correct...
The issue is that you currently can't leave nifi.web.http.host blank
because that will cause the "node API address" of each node to be
calculated as 'localhost', which then means replication of requests
Hi,
Is it possible to set the producer record timestamp within the
PublishKafka_1_0 / PublishKafkaRecord_1_0 processor?
I tried to use the "Attributes to Send as Headers" option with a
timestamp attribute, but this did not work. Not sure if the timestamp
producer record's timestamp is in
Hello Jon,
The number of processors is virtually unlimited, provided that you have
enough CPU to sustain the number of concurrent tasks allocated to NiFi to
provide acceptable performance, enough disk space for the NiFi
repositories, and enough RAM to cover the overhead of the processor
Hello,
We're running a secure 3 node 1.4 cluster. Has anyone seen any behaviour
where the cluster just stops scheduling the running of flowfiles/tasks?
i.e. cron/timer, just don't run when they're suppose to. I've tried to
stop and restart a processor that is say set to run ever 900sec, but
Hi Dan,
If all available Timer Driven Thread are being used (or hang
unexpectedly for some reason), then no processor can be scheduled.
The number at the left top the NiFi UI under the NiFi logo shows the
number of threads currently working.
If you see something more than 0, then I'd recommend to
Dev Team,
I am running into an interesting issue while trying to cluster NiFi in a
containerized environment (Docker containers running on DC/OS cluster) and
I am somewhat stuck with what to do. I am starting with getting just 2 NiFi
nodes with a single external zookeeper instance (just to get
10 matches
Mail list logo
