Member since
07-31-2018
10
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
570 | 10-04-2018 02:28 PM |
04-29-2019
02:50 PM
We have given 4GB of memory to heap by mentioning it in bootstrap.conf and all repositories (Content, Provenance, Content & FlowFileRepository) are configured to Disk. DistributedCacheServer is also configured to use disk. But when NiFi instance runs for a while It starts using 10 GB of memory. Not able to find where the extra 6 GB of RAM is consumed. Please help.
... View more
12-01-2018
08:33 AM
Thanks for the response. Configurations - How many flows? - did you mean messages in nifi? if yes, almost 45k messages flows as we are using splits and all. you can say almost 1.2 GB of data flows. What version of NiFi? - 1.7.1 What version of JDK? - 1.8 What host OS? - Redhat How much RAM on the system? System is having 32 Gb of RAM. 6GB is allocated to Nifi in bootstrap.conf. What kind of server? - What type of disk? - HDD
... View more
11-29-2018
08:38 PM
@Bryan Bende - I request you to please give your thoughts on it. Thanks in advance.
... View more
11-29-2018
08:38 PM
1 Kudo
According to our current implementation, we are restarting nifi once in a day becuase after lot of porcessing, either disk space or RAM is fully cosumed by Nifi. That is why we need to restart the nifi and we are not only restarting the nifi we are cleaning the below directories also - content_repository state logs run work database_repository provenance_repository flowfile_repository I know here is something wrong in our configuration and setup which is forcing us to restarting nifi once in a day and the above folder cleaning. Please help if you find something wrong in our process.
... View more
11-15-2018
07:38 AM
I want to run two nifi at one server. I know there are some configurations needed in nifi.properties to be changed, but I did what I found relevant. After doing changes in nifi.properties file still both nifi are not running in parallel.
... View more
Labels:
10-04-2018
02:28 PM
This is because I have not made the entry of that processor in below file /src/main/resources/META-INF/services/org.apache.nifi.processor.Processor We should make entry of processor in that file with the complete package path for e.g. org.nifi.processors.FileModifierProcessor
... View more
10-04-2018
10:17 AM
When I add a new custom processor in the code, At Nifi UI processor list is shown but the processor that I created is not coming in the list. Although it is added one time in the UI but when I am trying to add it again it is not coming in the processor list. And when I am trying to copy the existing processor then it says, not a valid processor type. What is wrong here?
... View more
Labels:
09-13-2018
07:33 AM
I copied flow.xml.gz in the conf directory and restarted the nifi. It is not detecting it. Don't know what goes wrong here. And the big thing is there is not such error in nifi-app.log and nifi-bootstrap.log file. What can we do? I am sure flow.xml.gz is not corrupted as the same file is working if I upload it in the other instance of nifi. Is there any difference while running nifi as service or as process(nifi.sh start).
... View more
09-07-2018
02:23 PM
For just one line change, Here is what I need to do - 1. Build the nar using Maven 2. Copy the .nar to lib directory 3. Restart the nifi (which takes too long) 4. Got some issue in changed code? do the above 3 steps again. 😄 You can see, How much longer the process is. It takes too long to do the development instead of thinking about any logic. Am I following the wrong approach? Please suggest if I am doing anything wrong here.
... View more
09-06-2018
10:23 AM
I have done some code changes, created a nar and pasted it in the lib directory and then restarted the nifi. But still nifi was having the old code. Then I removed the nar file from the directory and re-ran the nifi. Stranged, It is still having the code for the deleted nar. What to do to reflect the code changes done in the nar everytime we copy nar to the lib directory.
... View more
Labels: