Ah, thanks for the background! Whether or not you will have issues on fetching, replacing, and putting will depend on how big the file is, and how often this logic is happening. If it is 1200 iteration each time the logic runs and the logic runs every 24 hours then you will be fine. If it runs every 1 second then you may be hurting with this solution 🙂 A possibly better approach may be to use the ExecuteScript processor and write a simple Groovy or Python script that updates the file for you. Or you could potentially look at implementing some logic that would allow you to update the file only once at the end, if possible, instead of every one of the 1200 iterations, etc. ... View more

@mliem I think I misunderstood a little bit what you are trying to do. I thought you were trying to just append something to the end of the file each time. But it looks like you're actually trying to replace the value. So instead of appending to the file, in ReplaceText you can use the Regex Replace "Replacement Strategy." For example, the Search Value may be something like: (${count} ${TagName}),.* with a Replacement Value of: $1,${now():format('yyyy-MM-dd HH:mm:ss')} So if the 'count' attribute is 3 and the 'TagName' attribute is 'tag3' you would replace '3 tag3,2016-01-03 13:01:01' with '3 tag3,2016-06-29 13:16:33:50' for instance. Is this a little more along the lines of what you're looking for? ... View more

@Sai Dileep that log message indicates that the NiFi process has started, and it is listening for "shutdown" commands, etc. from the bootstrap. However, it does not indicate that the dataflow has started or that the web UI is ready. It will typically take 1-2 minutes to startup. Do you have anything else in the nifi-app.log file? If not, can you check the nifi-bootstrap.log file and see if there is something going on there? Additionally, in the conf/bootstrap.conf file, please make sure that you don't have the process setup to listen for a Remote Debugger. That would be done by looking for this line around line 39 in the file: #java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000 If you see that the above line is un-commented and that suspend=y, that could cause the process to not finish starting. ... View more

It looks like it cannot resolve the hostname 'provaha' to an IP address - can you check if the provaha is in your /etc/hosts file, or supply the FQDN instead? ... View more

You may also want to consider that JMS messages tend to be quite small, and before pushing to HDFS it may help to merge together many JMS messages so that you don't have a huge number of files in HDFS. You could use the MergeContent Processor to accomplish this. ... View more