[
https://issues.apache.org/jira/browse/NIFI-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226090#comment-17226090
]
ASF subversion and git services commented on NIFI-7959:
-------------------------------------------------------
Commit 59e00c4b6f941964e054d5921647f850b6831af3 in nifi's branch
refs/heads/main from Bence Simon
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=59e00c4 ]
NIFI-7959 Handling node disconnection in MonitorActivity processor
- Make reporting in clustered scope to dependent of expected cluster state in
order to prevent unexpected flow file emission
This closes #4642.
Signed-off-by: Mark Payne <[email protected]>
> Implement MonitorActivity disconnection management
> --------------------------------------------------
>
> Key: NIFI-7959
> URL: https://issues.apache.org/jira/browse/NIFI-7959
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Extensions
> Reporter: Simon Bence
> Assignee: Simon Bence
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MonitorActivity processor, when the node disconnects from the cluster, might
> still emit "inactive" message. This can happen when the scope is set to
> cluster level monitoring and the given node cannot reach shared state but has
> information only based on the local activity. This might lead to false
> inactivity alert, so it is desirable to prevent reporting until the node is
> disconnected and reconcile state after reconnection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
