You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "n h (JIRA)" <ji...@apache.org> on 2016/07/22 00:01:41 UTC
[jira] [Updated] (NIFI-2357) Component hot deployment
[ https://issues.apache.org/jira/browse/NIFI-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
n h updated NIFI-2357:
----------------------
Description:
Hot deployment of new/upgraded components is a critical requirement in may scenarios. A few suggestions are :
1. Hot deployment of new processors/components
2. Hot deployment of processors/components that are not used in current flow context
3. Rolling upgrades (in clustered deployments)
"Hot deploy of new processors" helps in two very usefule scenarios :
a) Development of complex processors that uses a few nifi services (where mock framework only helps partially). It is also very helpful in development environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : a few hours each month/year). In this situation we could build "upgraded processor" and use them as "new processor".
was:
Hot deployment of new/"upgraded components is a critical requirement in may scenarios. A few suggestions are :
1. Hot deployment of new processors/components
2. Hot deployment of processors/components that are not used in current flow context
3. Rolling upgrades (in clustered deployments)
"Hot deploy of new processors" helps in two very usefule scenarios :
a) Development of complex processors that uses a few nifi services (where mock framework only helps partially). It is also very helpful in development environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : a few hours each month/year). In this situation we could build "upgraded processor" and use them as "new processor".
> Component hot deployment
> ------------------------
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: n h
> Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in may scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components
> 2. Hot deployment of processors/components that are not used in current flow context
> 3. Rolling upgrades (in clustered deployments)
> "Hot deploy of new processors" helps in two very usefule scenarios :
> a) Development of complex processors that uses a few nifi services (where mock framework only helps partially). It is also very helpful in development environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time : a few hours each month/year). In this situation we could build "upgraded processor" and use them as "new processor".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)