@whoknows  While there s no exact date yet in the Apache NiFi community, I have seen discussions around it as recent as Apr 8th that suggests it will be happening very soon.  Possibly within the next week or two. Thank you, Matt ... View more

Thank you @MattWho   Your recommendation worked for me. I have updated bootstrap.conf file in nifi.  Was able to successfully enable DB controller service and persist data into Ignite database from Nifi. Details: Copied jvm parameters available in the file \apache-ignite-2.16.0-bin\bin\include\jvmdefaults.sh to \nifi-2.0.0-M2\conf\bootstrap.conf file Here is the format and exact list of java arguments added in nifi bootstrap java.arg.21=--add-opens=java.base/jdk.internal.access=ALL-UNNAMED java.arg.22=--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED java.arg.23=--add-opens=java.base/sun.nio.ch=ALL-UNNAMED java.arg.24=--add-opens=java.base/sun.util.calendar=ALL-UNNAMED java.arg.25=--add-opens=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED java.arg.26=--add-opens=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED java.arg.27=--add-opens=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED java.arg.28=--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED java.arg.29=--add-opens=java.base/java.io=ALL-UNNAMED java.arg.30=--add-opens=java.base/java.nio=ALL-UNNAMED java.arg.31=--add-opens=java.base/java.net=ALL-UNNAMED java.arg.32=--add-opens=java.base/java.util=ALL-UNNAMED java.arg.33=--add-opens=java.base/java.util.concurrent=ALL-UNNAMED java.arg.34=--add-opens=java.base/java.util.concurrent.locks=ALL-UNNAMED java.arg.35=--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED java.arg.36=--add-opens=java.base/java.lang=ALL-UNNAMED java.arg.37=--add-opens=java.base/java.lang.invoke=ALL-UNNAMED java.arg.38=--add-opens=java.base/java.math=ALL-UNNAMED java.arg.39=--add-opens=java.sql/java.sql=ALL-UNNAMED java.arg.40=--add-opens=java.base/java.lang.reflect=ALL-UNNAMED java.arg.41=--add-opens=java.base/java.time=ALL-UNNAMED java.arg.42=--add-opens=java.base/java.text=ALL-UNNAMED java.arg.43=--add-opens=java.management/sun.management=ALL-UNNAMED java.arg.44=--add-opens=java.desktop/java.awt.font=ALL-UNNAMED We just need to make sure java.arg.<>  numbers are unused in the bootstrap file that we are working on. Thanks again! ... View more

@tmarkfeld Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

@Ytch  All components on the NiFi canvas are executed as the NiFi service user and not as the user currently authenticated into the NiFi service.   So what you should do is from each host in your NiFi cluster (do on every host since any one of the hosts can be elected as the primary node at any given time), open a command prompt window/console window, become the user that owns the NiFi process, and manually ssh/sftp to the target SFTP server.  You will likely be prompted to add the target SFTP server to your known_hosts file for the NiFi service user.  NiFi SFTP processor has no way of doing this interactive step.  After successfully adding the SFTP to the known_hosts file for the NiFi service user, go back and try to start the GetSFTP or ListSFTP processors again to see if your issue is resolved. If not, please share your GetSFTP and ListSFTP processor component configurations. Also check the nifi-app.log for any exceptions or log output related to these processors. If no log output, you could also try enabling debug in the NiFi logback.xml for these processor classes to see what additional log output may be produced that could be useful here. classes for these processors are: org.apache.nifi.processors.standard.GetSFTP org.apache.nifi.processors.standard.ListSFTP new log lines would look like this that you would add to logback.xml: <logger name="org.apache.nifi.processors.standard.GetSFTP" level="DEBUG"/> <logger name="org.apache.nifi.processors.standard.ListSFTP" level="DEBUG"/> Simply add them in logback.xml where you see similar lines already. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Hi Matt, we configured 24GB as xms and xmx parameters. For now we have a normal use of memory without OOM errors. Thank you, Fortunato ... View more

Hi @MattWho    1) Initially, I faced the "NiFi PutSFTP failed to rename dot file issue" only when the child processor was configured with "Outbound Policy = Batch Output". It worked without the child processor group. 2) I modified the PutSFTP failure retry attempt to 3, and it fixed the issue. 3) Later, I introduced a RouteOnAttribute after the FetchHDFS processor for some internal logic implementation, and the PutSFTP error started again.  4) This time, I updated the "Run Schedule" of the PutSFTP processor from 0Sec to 3 Sec, and it again fixed the issue.  5) I have a requirement to transfer stats of each file (with file name, row count, file size) etc. So, I introduced one more PutSFTP processor, and the issue popped up again.  6) Finally, I made the following changes to both of my PutSFTP processors:        a) Added PutSFTP failure retry attempt to 3.        b) Modified the "Run Schedule" of the first PutSFTP Processor to "7 Sec".        c) Modified the "Run Schedule" of the second PutSFTP Processor to "10 Sec".   Now it is working fine. Are we getting this issue because of 20 flowfiles processing at a time ?  Could you please suggest if this is the right way to fix the "NiFi PutSFTP failed to rename dot file issue"? ... View more

@darkcoffeelake Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@Adhitya, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more