[
https://issues.apache.org/jira/browse/NIFI-11290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704270#comment-17704270
]
ASF subversion and git services commented on NIFI-11290:
--------------------------------------------------------
Commit 8eeebdb61402ebcceba326467aace9631517020d in nifi's branch
refs/heads/support/nifi-1.x from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8eeebdb614 ]
NIFI-11290 Run Component Primary Node State changes in background thread
- Ensure that components are notified that primary node has changed in a
background thread instead of the Leader Election thread and activate/deactivate
the thread in the case of Processors so that they can be viewed in the UI and
terminated
- Fixed system tests that would fail intermittently because they did not wait
for node disconnection to complete and did not properly switch the client to
look at the connected node before checking cluster status
This closes #7052
Signed-off-by: David Handermann <[email protected]>
> When Primary Node changes, components should be notified in a background
> thread
> -------------------------------------------------------------------------------
>
> Key: NIFI-11290
> URL: https://issues.apache.org/jira/browse/NIFI-11290
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When Primary Node changes, all components (Processors, Controller Services,
> Reporting Tasks) have the ability to be notified via the
> {{@OnPrimaryNodeChanged}} annotation. This is done in the FlowController from
> the LeaderElection thread.
> However, if a component blocks indefinitely, that thread is blocked, and
> there's no way to terminate it.
> This should instead be done in a background thread.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
