[
https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379338#comment-15379338
]
ASF GitHub Bot commented on NIFI-619:
-------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/575
Hi @JPercivall , let me try on this one more time.
Here's update summary:
- I've split the changes into two part: NIFI-2267 and NIFI-619.
- In NIFI-2267, only isClustered and isPrimary are exposed as
NodeTypeProvider for ProcessorInitializationContext. Not in ValidationContext
- NIFI-619 depends on NIFI-2267
- MonitorActivity doesn't validate property based on node types, instead,
if it's invalid fall back to a right configuration and log warning message so
that a DataFlowManager can notice
> update MonitorActivity processor to be cluster friendly
> -------------------------------------------------------
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Brandon DeVries
> Assignee: Koji Kawamura
> Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the
> cluster. In its current state, alerting is based on activity of a single
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given
> flow and system B is not, system B will alert for lack of activity even
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both
> systems did not see data in the specified time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
