[
https://issues.apache.org/jira/browse/NIFI-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368246#comment-15368246
]
ASF GitHub Bot commented on NIFI-2078:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/563
@ijokarumawak I am not opposed to performing the view / clear on primary
node only when NiFi is in clustered mode. That wouldn't have been a good idea
in the 0.x baseline because the primary node may be disconnected. But in 1.0 we
would auto-elect a new primary so I am ok with it in the 1.x baseline. For
external state, though, we would need some sort of indicator as to whether the
state should be cleared on all nodes or only the primary node. This could
perhaps be part of the ExternalStateManager interface - a "Scope
getStateScope()" method so that we know if external state is being managed
per-node or cluster-wide. This would tell us if we need to replicate the
request to all nodes or only the primary node.
> State management for processors whose states are managed externally
> -------------------------------------------------------------------
>
> Key: NIFI-2078
> URL: https://issues.apache.org/jira/browse/NIFI-2078
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Inherently by the nature of a given processor it may involve state managed by
> itself (using nifi state management), or can be managed by some external
> service it interacts with (kafka's offset), and theoretically some might have
> both going on. With the new state management, we're giving users a way to
> reset state managed by nifi for a given processor. But it doesnt apply to
> those processors who have external state.
> we should consider offering a way to reset state that allows a processor to
> call out to whatever external store it impacts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
