Re: nar install in Nifi

[Andy LoPresto <al...@gmail.com>]

No, because of the class loading and general lack of Java hot swap capability, to add or replace NAR files, the application must be restarted. 

Is your prohibition on restarting the app due to the need for "100%" uptime or a different reason? If you deploy a cluster, you can do a rolling update where one node is stopped, the NAR deployed there, and then restarted and move across your cluster repeating this process. You will still have functioning nodes that cover the entire process. 

If the prohibition is just against restarting NiFi at all, I'm not sure how you will do security updates or bug fixes, but you can still deploy new functionality by using the ExecuteScript or InvokeScriptedProcessor components, or invoking Java classes via the command line and ExecuteStreamCommand or ExecuteProcess components. 

Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Nov 25, 2016, at 03:22, <sa...@wipro.com> <sa...@wipro.com> wrote:
> 
> Hi Nifi Developers
> 
> Every time I want to add a custom processor to nifi, I need to restart nifi.
> But in production I will not be allowed to restart Nifi. So is there a way to install new nar files without restarting nifi.
> 
> /BR
> Santosh
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

Re: nar install in Nifi

[Joe Witt <jo...@gmail.com>]

As we progress the extension registry concept we will provide for
versioned components which will also mean we can have multiple
versions of the same component on the same flow at the same time.  In
this case we can do a pretty nice live loading of new capabilities
since it totally side steps the issue of actual hot swapping.

Although to Andy's point there are times when you definitely want a
real restart of a node and you can still get the always on uptime
effect with rolling upgrades of a cluster.

Thanks
Joe

On Fri, Nov 25, 2016 at 8:04 PM, Andy LoPresto
<al...@gmail.com> wrote:
> No, because of the class loading and general lack of Java hot swap capability, to add or replace NAR files, the application must be restarted.
>
> Is your prohibition on restarting the app due to the need for "100%" uptime or a different reason? If you deploy a cluster, you can do a rolling update where one node is stopped, the NAR deployed there, and then restarted and move across your cluster repeating this process. You will still have functioning nodes that cover the entire process.
>
> If the prohibition is just against restarting NiFi at all, I'm not sure how you will do security updates or bug fixes, but you can still deploy new functionality by using the ExecuteScript or InvokeScriptedProcessor components, or invoking Java classes via the command line and ExecuteStreamCommand or ExecuteProcess components.
>
> Andy LoPresto
> alopresto@apache.org
> alopresto.apache@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>> On Nov 25, 2016, at 03:22, <sa...@wipro.com> <sa...@wipro.com> wrote:
>>
>> Hi Nifi Developers
>>
>> Every time I want to add a custom processor to nifi, I need to restart nifi.
>> But in production I will not be allowed to restart Nifi. So is there a way to install new nar files without restarting nifi.
>>
>> /BR
>> Santosh
>> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com