[
https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377257#comment-15377257
]
ASF GitHub Bot commented on NIFI-619:
-------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/575#discussion_r70840662
--- Diff:
nifi-api/src/main/java/org/apache/nifi/components/ValidationContext.java ---
@@ -99,4 +100,9 @@
* @return the identifier of the ProcessGroup that the component being
validated lives in
*/
String getProcessGroupIdentifier();
+
+ /**
+ * @return the {@link NodeTypeProvider} which can be used to detect
the node type of this NiFi instance.
+ */
+ NodeTypeProvider getNodeTypeProvider();
--- End diff --
Agreed. I was thinking it'd be too much. Exposing primary state was not
what I wanted, though.. Processor's property descriptors and validators are
often defined in static scope, and I thought if ValidationContext provides
cluster or not, it's useful.
I'll remove this.
> 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)
