[jira] [Commented] (NIFI-8300) Make non-source processors invalid if scheduled for Primary Node only

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304951#comment-17304951 ] 

ASF subversion and git services commented on NIFI-8300:
-------------------------------------------------------

Commit fedeafb43fe150db4e00c426bb13777aa8ae8a70 in nifi's branch refs/heads/main from s9514171
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fedeafb ]

NIFI-8300 Make non-source processors invalid if scheduled for Primary Node only

This closes #4913.

Signed-off-by: Mark Payne <ma...@hotmail.com>


> Make non-source processors invalid if scheduled for Primary Node only
> ---------------------------------------------------------------------
>
>                 Key: NIFI-8300
>                 URL: https://issues.apache.org/jira/browse/NIFI-8300
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Hsin-Ying Lee
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> There is never a reason a to schedule a processor to run on Primary Node Only unless the processor is a source processor. However, we see this misused fairly frequently, and it can result in data not moving through the system. We should update the processor validation logic so that a processor is made invalid if has an Execution Node of Primary Node Only and has any incoming connections.
> This includes self-looping connections. Otherwise, Node A can be primary node, and then queue up data. Node B then becomes Primary Node, leaving data sitting on Node A indefinitely. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)