@vikrant_kumar24   To add new attributes to a flow file you should use UpdateAttribute.  To get attributes from json you should use EvaluateJsonPath.  Once you have all the values you want as attributes you should use AttributesToJson and then finally send the json to invokeHttp.   Your flow will look like this:   And the Queued Flowfile waiting on InvokeHttp is:   Please note I did not have your original Json, just the schema above, so I created a simple JSON of the Longitute & Latitude values you gave me.    I also did not touch InvokeHttp, its default.   Once you get this far, and want to work on handling the response from InvokeHttp let me know here, in another post, or a private message.   To see my entire template, check out my GitHub for the Invoke Http Demo 2 Template:   https://github.com/steven-dfheinz/NiFi-Templates     If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.     Thanks, Steven @ DFHZ ... View more

@keithg  If you change the 1 sec to 15 sec or 30 sec does it become more stable?   With the schedule set to 1 sec, invokeHttp will execute 1600 connections as fast as possible.  This opens up quite a bit of room for either exceeding the capabilities of your environment (not enough nodes, ram or cores) or the upstream service you are connecting too (actual network issues with the workload).   Since you only have 2 cores, you need to sensitive to tuning the flow, and most likely need to go slower (ie not 1 sec).  You should also investigate documented NiFi Performance Tuning Steps, adding a lot more cores, adding more ram to each node including min ram: 2-6 gb max ram: 4-8-16 gb, and/or adjusting Garbage Collection. ... View more

@keithg Can you update the post with the scheduling settings for InvokeHttp?  Also would nice to see  some specific details about the nifi environment (min/max memory settings, nifi node spec, disk config, etc) and setting for min/max threads?   Without taking those things in consideration, I would assume you are overloading capability resulting in instability you are experiencing.  If you slow down the scheduling and consume the incoming queue at a slower rate, does the timeout persist? ... View more

@satishjan1 the command to set the hostname is:   hostnamectl set-hostname host.name.com Depending on your OS config, you may also need to update items that may manage that hostname and the host files.  You can confirm by doing above, and then reboot.   The hostname should persist after reboot.     If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.     Thanks,   ... View more