Huagen,
You can possibly avoid it by giving NiFi a large heap size. The
downside is that there is a good library I am aware of which will let
us handle large remote listing as nicely as we'd like. It does tend
to be a 'send small request', 'wait for a large reply', 'then process
large reply' pat
Hello Kumiko
The ProcessSession API exposes to you the ability to adjust counters [1].
You would simply call that in your on trigger method with something like
session.adjustCounter("mycounter",1L,true);
[1]
https://github.com/apache/nifi/blob/master/nifi-api/src/main/java/org/apache/nifi/proc
You could generate a unique filename with that extension by using the
following in Update Attribute
Add property:
property name: filename
property value: ${uuid}.json
You can also set a directory structure with time stamping this way as
well. For instance set another attribute on that Update
Hello
While i am not aware of any strong reason to keep it the way it is there
are no plans to change it at this time. Some project do this and some
don't.
Thanks
Joe
On Jun 6, 2016 10:13 AM, "ski n" wrote:
> Yes, I already have a soft link, but this was more a remark that the
> directory stru
Tom,
I suspect some others might add some additional info here but to
achieve the back-up of the configuration such that you could quickly
restore you'd generally just need to save the conf directory content.
The flow configuration should port well to another node including the
sensitive property
Leslie
You could update the flowfile queue swap threshold higher in such a case.
That said at that size of a heap you may see undesirable GC behavior.
Simply put what you saw when making tons of tiny flowfiles after a split
and it causing slowness is a bug and should be fine on far smaller heaps.
Hello
Your request for dates on the release notes seems fair to me. I went
ahead and added them there assuming nobody has any objection. We
generally try to follow a rough 6-8 release cycle. It will be a
little longer or a littler shorter sometimes. Right now for example
we're trying to close
Hello
I think this is a good idea. Can you submit a jira please.
Thanks
Joe
On Jun 7, 2016 11:12 PM, "N H" wrote:
> Hi,
> Why funnels missed name property ? It is very handy when using API to
> manage flows (non-graphical batch clients),
>
Keith,
Can you collect more information on this from the nifi-app.log? Not
in valid state should be associated with some exceptions and such that
ideally will be in the logs.
Thanks
Joe
On Wed, Jun 8, 2016 at 1:00 PM, Keith Lim wrote:
> Any help on this before while I am upgrading my NiFi to 0
Pat
Could you please make sure we are seeing the full stacktrace from the app
log? If we could get a full log that would he even better.
Thanks
Joe
On Jun 11, 2016 1:17 PM, "Pat Trainor" wrote:
> Andrew,
>
> Thanks for writing.
>
> *Nifi:*
> nifi-0.6.1
> *Kafka:*
> kafka_2.11-0.10.0.0
>
> star
Pat,
GetTwitter does produce single tweet outputs and the example you
provided I believe is actually a single tweet. Try pasting that into
a json formatter and I think you'll find it is a single tweet.
'created_at' is used on several entity types in twitter is appears so
that isn't telling you ab
...i wonder if we've done the same ourselves or given similar advice
to others. This feels like something the framework should make
available as an expected lifecycle point. I could see it making sense
for such cases that we would allow 'OnScheduled' to be on controller
services and let the user
Eric
You aren't doing anything wrong. It is indeed something that can be quite
annoying and with the upcoming 1.0 release is solved.
Taking turns is the current answer and we typically see operations teams
coordinate via chat. However we can do far better. If you want an advance
look at this y
Pat,
I'll respond wearing my Apache member and Apache NiFi PMC hats.
No.
NiFi is of the Apache Software Foundation and thus cannot be bought.
That said to the spirit of your question it is fair to ask whether
this community is diverse in its representation of members and who
they are employed
Agreed - it should work out of the box.
When you run 'java -version' can you please share the output.
Thanks
Joe
On Tue, Jun 28, 2016 at 7:23 AM, Scott Stroud wrote:
> Im attempting to use the InvokeHTTP component with the 0.6.1 release and
> keep seeing this error. My JAVA_HOME is 1.8.0_72-b1
AM, Scott Stroud wrote:
> java version "1.8.0_72"
>
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
>
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
>
>
> On Tue, Jun 28, 2016 at 10:27 AM, Joe Witt wrote:
>>
>> Agreed - it
s almost as if it's detected the wrong platform.
>>>>
>>>> Not an answer but the Android reference is probably from there.
>>>>
>>>> > On Jun 28, 2016, at 7:37 AM, Joe Witt wrote:
>>>> >
>>>> > Scott
>>&
Kevin,
Can you get us the full log entry and/or stack dump for this.
Thanks
Joe
On Thu, Jul 7, 2016 at 3:58 PM, Kevin Verhoeven
wrote:
> I am running on version 0.7.0.
>
>
>
> I am generating files using the GenerateFlowFile Processor to create a batch
> of 1,000 unique text flowfiles of 1 KB e
Hello
Take a look here
https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Controller_Settings
You probably want this to be higher than the default value.
Thanks
Joe
On Wed, Jul 13, 2016 at 7:21 PM, Kevin Verhoeven
wrote:
> I am running a NiFi cluster (0.7.0 snapshot) that contains 19
Mike,
If you don't mind could you file a JIRA for this. Frankly it sounds
like a bug to me. We should consider making a default scheduling
period of something a bit slower. Frankly just dialing back to 100 ms
would be sufficient most likely. If you agree this is a bug please
file one here: htt
Mans,
The general pattern for something like this that works well is:
- Capture
- Split
- Site-to-Site transfer back to same cluster which distributes the
partitioned/split data to all nodes
- Do work on smaller chunks
We often do exactly this sort of thing for larger scale geo enrichment
for
Hello
You should certainly be able to execute a local script (local to the
server NiFi is running on). That local script can execute remote
commands (on systems other than NiFi is on). In this manner NiFi
usage would be basically as a cron tool which isn't its primary
purpose but is an edge case
Stephane,
Yes, you'll want to create a new processor and package it within a Nar
with proper licensing and dependency management. You'd be
establishing a reusable and self-contained bundle that will
automatically work nicely within the UI, have documentation generated
from your annotations, and h
Sven,
We do monitor threads which have been given to processors but not
returned. You can see them through the REST API and UI both on the
processor itself showing thread count and in the summary pages.
For the onTrigger calls of a processor we do not time bound them and
kick out the threads. W
Jake,
Can you give \\n a try on the regex replace strategy? Let us know if
that does it.
Thanks
Joe
On Thu, Jul 21, 2016 at 11:18 PM, Jake Kugel wrote:
> Hello,
>
> Is it possible to use ReplaceText processor to insert a newline character
> (0x0a) or other special characters into a flowfile?
the flowfile instead of 'n'.
>
> Jake
>
>
> On 7/21/16 10:22 PM, Joe Witt wrote:
>>
>> Jake,
>>
>> Can you give \\n a try on the regex replace strategy? Let us know if
>> that does it.
>>
>> Thanks
>> Joe
>>
>>
Sravani,
So process group one executes two parallel flows and its output comes
together on the same port.
Those two outputs flow through that port and into process group two.
Are you saying you want to make sure the processes in process group
two do not fire until both outputs are available?
If
Hello
The way site to site works today it takes care of the automated
fail-over and load balanced delivery between NiFi Clusters. We did
not, however, make it so that in failure cases you could then elect to
send the data down an alternative path.
That certainly is a good idea and please do file
Devin,
In the more recent versions of NiFi attempts to stop the processor
which are not successful after some period of time (I think 30
seconds) should result in the process being killed if possible and
NiFi should then move on again.
What version are you on?
Thanks
Joe
On Fri, Jul 22, 2016 at
Thanks Brian. Will discuss on the JIRA. If you could possibly share
the stack dumps for anything involving the prov repo that would be
really helpful.
Thanks for reporting and also providing really helpful context/analysis.
Joe
On Tue, Jul 26, 2016 at 9:23 PM, Brian Davis
wrote:
> I have been
Aaron, Mark,
In looking at the thread-dump provided it looks to me like this is the
same as what was reported and addressed in
https://issues.apache.org/jira/browse/NIFI-2395
The fix for this has not yet been released but it slated to end up on
an 0.x and 1.0 release line.
Mark do you agree it i
ly useful.
>>
>> Joe,
>>
>> I do indeed believe this is the same thing. I was in the middle of typing
>> a response, but you beat me to it!
>>
>> Thanks
>> -Mark
>>
>>
>> > On Aug 1, 2016, at 11:49 AM, Joe Witt wrote:
>> >
that should make me worried about running it on a production
> flow?
>
> -Aaron
>
> On Mon, Aug 1, 2016 at 4:01 PM, Joe Witt wrote:
>>
>> Aaron,
>>
>> It doesn't look like the 0.x version of that patch has been created
>> yet. Any chance you c
Andrew,
You are right that it is a common request and desire and the
dev/stagin/prod lifecycle you mention makes sense and is also common.
In the upcoming nifi 1.0 release a variable registry has been
introduced which will allow you to do exactly what you show above for
any property of any compo
Hello
There are no processors included in the apache release that
specifically operate on netflow so you'd need to have a custom
processor to deal with it until one is included.
Netflow is often flowing through NiFi typically for things like
content merging and loading into HDFS. Parsing is a go
I like what Mark suggests but if you're not sure how many fragments
there will be during the flow for a given group then I think you could
keep doing what you were but set it to some really high min count and
min size and then have a time based kick out that waits long enough
where you're confident
Probably a good idea to use a script in a script processor to extract
the details needed about the splits then feed those results into merge
attribute as you suggested. This would be the safest/cleanest.
On Wed, Aug 10, 2016 at 3:42 PM, Mark Payne wrote:
> Michael,
>
> Well, sort of...
>
> You c
Hello Sven
LogAttributes will just show the attributes as they are understood by
the flow file itself. But the PutSQL processor may be doing something
more specific with the data. Can you share your configuration for
PutSQL?
Thanks
Joe
On Fri, Aug 12, 2016 at 7:05 PM, Sven Davison wrote:
> Ac
Adding jars to the lib directory is not ideal as it pollutes all
classloaders. We should add expression language support to the path
property if it isn't already as that makes variable registry access
available which makes use of the same template or flow in different
environments easier.
On Aug
ed? I have one JDBC driver that for
> whatever reason requires two separate JAR’s.
>
>
>
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Friday, August 19, 2016 5:30 AM
> To: users@nifi.apache.org
> Subject: RE: adding dependencies like jdbc drivers to the build
Jim
The case you outline is quite common, critical for a system like this
to handle well, and is something nifi offers some good options for.
So for a processor like PutFile it is quite fine to loop failure back
to itself. What you want to do is consider if you want guaranteed
delivery and if so
also this is a great use case which has been done quite a bit in the
past using exactly the sort of logic Bryan calls out. We've also done
things like written custom controller services specific to the type of
data and data structures needed for the job. But the
plumbing/infrastructure for it is
Hello Gunjan,
>From looking in the email archives here, recent conference talks and
keynotes, and some quick Internet searches we see strong
representation across Fortune 500 companies in retail, financial
services, healthcare, oil and gas, and automotive.
We should eventually do as other communi
Gunjan
We've long since supported the concept of flow templates. These are
powerful because they allow you to save, share, import already
designed flows. They have to date had their full potential limited by
a few things:
1) The exported template was non-deterministic in terms of the XML it
pro
Gunjan
We have a feature proposal for this. Def a good idea that will help
simplify flow development. It makes for process groups as functions. No
clear time table for when it might happen but check out the feature
proposal and comment on it and join the discussion.
Thanks
Joe
On Aug 29, 2016
Lorenzo
Without seeing the code and logs it would be very difficult to help. nifi
has no trouble by design writing large files (GBs) to many things including
hdfs so the issue is probably in how this client library interacts with the
data stream.
On Sep 2, 2016 4:19 PM, "Lorenzo Peder" wrote:
You would need to make a custom process for now. I think we should have a
nice controller service to generalize jdbc lookups which supports caching.
And then a processor which leverages it.
This comes up fairly often and is pretty straightforward from a design
POV. Anyone want to take a stab at
Def not. We need to figure out what it is not detecting.
On Sep 4, 2016 10:25 AM, "Shashi Vishwakarma"
wrote:
> Thanks . It worked. Do I need to remove directory everytime when i change
> controller service?
>
> On Sun, Sep 4, 2016 at 7:03 PM, Matthew Clarke
> wrote:
>
>> When nifi starts it u
Dan
I do recommend going the custom processor route. You could initially do
that using InvokeScriptedProcessor to figure out any intracacies then turn
it into a full blown proc later.
Thanks
Joe
On Sep 4, 2016 2:51 PM, "dgm" wrote:
> Hi Andre,
>
>
>
> Thanks for the reply. Agree with you.
Shashi
You should not have to enter the controller service identifier. In your
processors property descriptor have you used 'identifiesControllerService'
set. Such as in this example
static final PropertyDescriptor SSL_CONTEXT_SERVICE = new
PropertyDescriptor.Builder()
.name("s
Gunjan
The best indicator of areas of focus I think are listed here
https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals
In a roadmap discussion thread back in January of this year the items
mentioned specifically as trailing the 1.0 release were extension and
variable registri
Joe,
> w.r.t to NiFi externals, like we currently have NiFi spark and storm
> externals, any plans for NiFi beam external? Reason is I saw your name as
> one of the contributors there in incubation proposal.
> I was studying beam in more depth hence the question.
>
>
> On
gt;>
>>
>> Thanks
>>
>> Kumiko
>>
>>
>>
>> *From:* Tony Kurc [mailto:trk...@gmail.com]
>> *Sent:* Tuesday, September 6, 2016 3:02 PM
>> *To:* Kumiko Yada
>> *Cc:* users@nifi.apache.org; Joe Witt ; #Operations
>> Automation and T
Tijo
Most conf file related changes are intentionally application startup
based. Which properties are you having to change that you'd like to
see honored without a restart?
Thanks
Joe
On Wed, Sep 14, 2016 at 10:44 PM, Tijo Thomas wrote:
> Hi
>
> Our nifi cluster need to be up continuously as o
Hello
Please only post to one list. I have moved 'dev@nifi' to bcc.
In the docs for this processor [1] you'll find reference to "Multipart
Part Size". Set that to a smaller value appropriate for your JVM
memory settings. For instance, if you have a default JVM heap size of
512MB you'll want so
It would buy time but either way it becomes a magic value people have
to know about. This is not unlike the SplitText scenario where we
recommend doing two-phase splits. The problem is that for the
ProcessSession we hold information about the flowfiles (not their
content) in memory and the proven
Ashish,
If the question is 'at runtime what are the ways I could trigger the
creation of a NiFI template?'
You could call the REST API endpoint using some mechanism other than
the NiFi UI or you could use the NiFi UI.
If the question is 'can I programmatically create a template during
developm
Great timing. Pierre put in a JIRA/PR for this yesterday.
https://issues.apache.org/jira/browse/NIFI-2832
Thanks
Joe
On Wed, Sep 28, 2016 at 8:22 AM, Bryan Bende wrote:
> Hi Selvam,
>
> It depends what processor you are using. For example, ListFile using a local
> file path will always store
Is "Use Chunked Encoding" set to false (as is the default) or has that
been changed to true? You'll probably need that set to true.
Thanks
Joe
On Wed, Sep 28, 2016 at 10:26 AM, Selvam Raman wrote:
> Hi LoPresto/Villard,
>
> yes i am fetching data from an (OAI)open source server to my s3 bucket.
Hello
Can you talk a bit about why you'd want ListenTCP processors tied to a
given sensor? You should be able to have many sensors to a single
ListenTCP. Each stream will be between a source/sensor and nifi so
data won't be getting intermingled there. If we're not providing
enough session/strea
Roger,
For people coming to NiFi from traditional ETL/ELT systems we're
seeing a couple patterns emerge. They tend to want to view each flow
discretely and have used other systems that way and are trying to use
NiFi that way. And they tend to want a variety of relational
data/database type const
NiFi only writes data to disk when it is actually changing the data.
It is very uncommon to have a 10 processor flow where all or even most
are actually touching the content. You can take a look at the live
status history data to see exactly how much content is being read from
disk and written to
Nice find and thanks for the contrib/fix! Already merged.
There are plenty of things in already for a release to be worthwhile. Will
have the discussion on dev.
Thanks
On Mon, Mar 12, 2018 at 12:12 PM, Jorge Machado wrote:
> Yes,
>
> I opened a PR: https://github.com/apache/nifi/pull/2531/fi
Jorge
We dont generally publish a roadmap as they're really difficult to
have any real detail/stability behind them. What we do is generally
release couple months and we've started a discussion to put out Apache
NiFi 1.6.0 soon with the release candidate/vote process starting
ideally next week.
Kevin,
We have talked about this a bit in the past.
If you leverage versioned flows and you accidentally move or even make
changes to the flow you could simply rollback the version to get in
sync again.
We could also add a way to enforce a read-only sort of view mode but
there has never been muc
ture for the UI? I often move
> or change a processor and would really LOVE to be able to click undo.
>
> Thanks,
>
> Kevin
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Wednesday, March 14, 2018 11:27 AM
> To: users@nifi.apache.org
if its going to make it into the release.
>
> Thanks
>
>
> Kiran
>
>
>
> Original Message
> On 14 Mar 2018, 15:00, Joe Witt < joe.w...@gmail.com> wrote:
>
>
> Jorge
>
> We dont generally publish a roadmap as they're really difficul
Can you share a template of your process group?
Do the messages in Kafka have the Avro schema included in them or are
they just the data portion of the record?
On Wed, Mar 21, 2018 at 9:16 PM, Colin Williams
wrote:
> I have an avro avsc file for a table with a definition like:
>
> {"type":"recor
> I don't believe the Avro schema included, and expect they are the data
> portion... I think that's why I need to use the avsc file mentioned above...
>
> On Wed, Mar 21, 2018 at 6:19 PM, Joe Witt wrote:
>>
>> Can you share a template of your process group?
>>
tp://apache-nifi-users-list.2361937.n4.nabble.com/Nifi-1-3-0-Problem-with-schema-name-and-ConsumeKafkaRecord-0-10-processor-td2256.html
>>> That's why I moved away from using ConsumeKafkaRecord and to the regular
>>> consumer. I didn't want to create a properties file and
Scott
Yep definitely something we've talked about [1]. We've not pursued it
directly as of yet since it is indeed a queue and we're just letting
you peak into it. We dont have facilities built in to really alter
the queue in a particular position. Also, the complexity comes in
when folks want to
dan
It is presently working through the release candidate vote process. As it
stands now it could be out tomorrow.
Please do help by reviewing the rc if you have time. If you have questions
on how to do it just let us know and we can help.
thanks
joe
On Thu, Apr 5, 2018, 1:46 PM dan young wr
Hello
The Apache NiFi team would like to announce the release of Apache NiFi 1.6.0.
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, an
Jon,
Node Failure:
You have to care about two things generally speaking. First is the
flow execution and second is data in-flight
For flow execution nifi clustering will take care of re-assigning the
primary node and cluster coordinator as needed.
For data we do not at present offer distribute
Independent of NiFi have you successfully used any version of Jython
to make that call?
With the NiFi 1.x line that processor has been updated a little bit
and in particular i think we have Jython 2.7.1 (off memory so could be
totally nonsense) where as before we had 2.7.0 or something older...
T
James,
You have it right about the proper solution path.. I think we have a
Redis one in there now too that might be interesting (not in 1.3.0
perhaps but..).
We offered a simple out of the box one early and to ensure the
interfaces are right. Since then the community has popped up some
real/st
Laurens,
The recommended model in terms of capability/performance/flexibility
would be to use the Record Readers/Writers and associated processors
as Andy was hinting at. The approach you took was the simplest and
will perform fine up to say a few thousands per second. If you need
faster then th
Dann
The hadoop processors as of a version around 1.2.0 switched to
'instance class loading' meaning that while we always have components
from various nars in their own classloader in the case of Hadoop
processors we went a step further and we create a new classloader for
every single instance of
Hello
What version of NiFi are you on? Can you share more about the
controller services/specific processor combinations where you're
seeing this?
Thanks
On Thu, May 3, 2018 at 4:05 PM, Cassidy, Thomas G (Tom) JR CTR USARMY
MEDCOM JMLFDC (US) wrote:
> We are relatively new users of NiFi and thi
Boris,
can you share more about the context in which you were told it would
be a bad idea? There might be an important clarifying point there.
The pattern is certainly useful so we want to get the right messaging
around it.
Thanks
On Thu, May 3, 2018 at 4:17 PM, Shawn Weeks wrote:
> The rest a
hello
which processor are you seeing this on?
which version?
thanks
On Thu, May 3, 2018, 6:11 PM Tian TD Deng wrote:
> Dear all,
>
> The CPU usage of Nifi would raise to 100% if the "run schedule" property
> of Processor was set to 0.
>
> Set it to 1 would decrease the CPU but it has impact on
Scott
Can you share more about processors/styles that you find yourself
changing often? I've not seen cases where this would be important
personally but with 250+ components I concede there may well be many
such cases.
Thanks
On Fri, May 4, 2018 at 10:06 AM, Charlie Meyer
wrote:
> We solved th
Andrew,
I do agree with you point. I think Ryan's saying we need to do a
better job of calling that out in the docs/guiding folks to the best
path so they don't try combining older practices with ones that are
meant to totally replace it.
Is there more to it Ryan?
Thanks
On Mon, May 7, 2018 at
Hello
I suspect you're on a version older than the latest (1.6.0). This was
resolved in the latest release
https://issues.apache.org/jira/browse/NIFI-4925
Thanks
Joe
On Mon, May 7, 2018 at 8:50 AM, wrote:
> We’re using Ranger to provide LDAP group-based authorization to NiFi
> resources via t
t; *Subject:* RE: [Non-DoD Source] Re: Starting controller services
>
>
>
> Nagios XI. How do I determine which version? I suspect its recent but not
> the latest.
>
>
>
> Here are a couple of the controllers in use at the Process Group
> Configuration level.
>
&g
Mike,
This is really cool. There are a few websites around that keep handy
links for things like this but we should really start doing a better
job of encouraging the community to list their nifi extensions that
cannot go into the official Apache release here [1].
[1] https://cwiki.apache.org/co
Andres
Welcome to nifi. There are a lot of user guides, web pages, training
materials, youtube videos, and such to help you get going. I'd
definitely recommend starting from there to familiarize yourself with
NiFi. Setup some kind of simple self contained local flow to try
things out and get a
Mike
That could be cool - though we'd probably first want to reach out to
the Kylo community and ask them to contribute it directly rather than
just grabbing a copy.
Thanks
On Fri, May 11, 2018 at 10:56 AM, Damian Czaja wrote:
> Here is a great repo with a lot of information about NiFi and tool
Tim,
The default configuration for provenance event retention is
potentially a factor.
Did you make any changes to those? Can you share relevant segments
from the nifi.properties file?
Thanks
On Mon, May 21, 2018 at 8:32 PM, Tim Dean wrote:
> Hello,
>
> I am having a hard time troubleshooting
ed when the event is retrieved.
> nifi.provenance.repository.max.attribute.length=65536
> nifi.provenance.repository.concurrent.merge.threads=2
> nifi.provenance.repository.warm.cache.frequency=1 hour
>
> # Volatile Provenance Respository Properties
> nifi.provenance.repository.buffer.size=10
>
>
> Thanks
seems to me that my old data is still there and my new data is not.
>
> -Tim
>
>
>> On May 22, 2018, at 12:15 PM, Joe Witt wrote:
>>
>> Tim
>>
>> Got ya. So yeah keep in mind you'll only have at most 1GB of prov
>> data and for at most 24 hour
jim
please only post to one list.
users is good for this.
thanks
joe
On Tue, May 29, 2018, 3:54 PM James McMahon wrote:
> Good evening. I have recently migrated my nifi service host server from
> local resolution of users and groups to use an LDAP server. I configured
> login-identity-provider
Hello
Is this a single instance with wildcarding of topics? Please share config
details.
If you want that in a single instance you may need to alter the timeout
associated with any single kafka consumer. The assignment will be per
topic per partion. How many he threads for that processor?
Fin
timer driven thread count is set to 40)
>
> We tested the whole data flow with about 15-20 consumers and everything
> worked fine with out any errors. We started getting all these wired errors
> as soon as we bumped up our load test with 150+ consume kafka processors.
>
> On Mon,
Prasanth
I strongly recommend you reduce your JVM heap size for NiFi to 2 or 4
and no more than 8GB. The flow, well configured, will certainly not
need anywhere near that much and the more ram you give it the more
work GC has to do (some GCs are different and can be tuned/etc.. but
...that is for
Kelsey
Have you looked at JSONTreeReader?
thanks
joe
On Thu, Jun 21, 2018, 5:00 AM Kelsey RIDER
wrote:
> OK, thanks for the heads-up!
>
>
>
> If I could make another suggestion: could the JSONPathReader be made a
> little more dynamic? Currently you have to specify every single field…
>
>
>
>
you can allow for larger backlogs by increasing the backpressure thresholds
OR you can add additional nodes OR you can expire data.
The whole point of the backpressure and pressure release features are to
let you be in control of how many resources are dedicated to buffering
data. However, in the
Hello
Please post to just one mailing list. This is a good question for users.
Presently the 5 min window isn't configurable. However, on each
component we do have a status history you can access that is retained
longer (24 hours by default) and is configurable [1]
Thanks
[1]
https://nifi.ap
Hello
Sounds like possibly a caching issue. Try doing a hard cache
clear/refresh in your web browser.
Thanks
On Mon, Jul 16, 2018 at 2:20 PM, Jean-Sebastien Vachon
wrote:
> Hi all,
>
>
>
> I just upgraded my 1.4.1 cluster to 1.7.1 and discovered that the top right
> menu is not opening when cl
hello
when it appears to be stuck can you capture a thread dump?
bin/nifi.sh dump
and share content of logs dir.
thanks
On Wed, Jul 18, 2018, 3:28 PM Shawn Weeks wrote:
> You're probably hitting NIFI-5109. If NiFi goes through an election it
> loses its state for the List Processors.
>
601 - 700 of 1121 matches
Mail list logo
