[
https://issues.apache.org/jira/browse/NIFI-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379592#comment-15379592
]
ASF subversion and git services commented on NIFI-2267:
-------------------------------------------------------
Commit 53326c7f9bad7322893664f9a7bc1d36399049bf in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=53326c7 ]
NIFI-2267: A way for Processor to know node type
- Added NodeTypeProvider to expose flowController's isClustered and
isPrimaryNode so that processor can know if it's running on a cluster
and if it's a primary node.
- Added mechanism to simulate clustered or not, and primary or not, for testing
This closes #657
Signed-off-by: jpercivall <[email protected]>
> Provide a way for Processor to determine running NiFi node type -
> standalone/clustered, primary/node
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-2267
> URL: https://issues.apache.org/jira/browse/NIFI-2267
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Fix For: 1.0.0
>
>
> Currently, there's no way for processor to understand if it's running on:
> - Standalone or Cluster?
> - If in a cluster, is it a Primary node or not?
> There're processors that need this information to provide more cluster
> friendly behavior, such as MonitorActivity.
> @OnPrimaryNodeStateChange annotation is already available. However, it's
> notified only when a primary node has been changed. So, If a processor is
> added to an existing NiFi cluster, which has already one node elected as a
> primary node, the processor is not notified, thus it won't be able to know
> it's a primary node.
> This ticket is meant for tracking the effort of adding such capability to
> provide node type information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
