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

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

Commit ae6ad0556f78efa649485ce3da52d642976614fb in nifi's branch 
refs/heads/HDF-3.1-maint from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ae6ad05 ]

NIFI-5012: When connecting to cluster, esure that controller services 
appropriately enabled/disabled

This closes #2579.

Signed-off-by: Bryan Bende <[email protected]>


> Controller Services are not automatically enabled/disabled when joining 
> cluster
> -------------------------------------------------------------------------------
>
>                 Key: NIFI-5012
>                 URL: https://issues.apache.org/jira/browse/NIFI-5012
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.6.0
>
>
> If a node is disconnected from the cluster, a user is able to navigate to the 
> disconnected node and stop processors/controller services. Upon re-joining 
> the cluster, the node should inherit the cluster's run state for all 
> components. This works for processors but appears not to enable controller 
> services as expected. To duplicate, we can create a simple flow, as attached 
> in a template.
> Disconnect one node from the cluster. Navigate to the disconnected node, 
> disable the CSVReader controller service. Now re-join back to the cluster. 
> When the node rejoins, instead of the Controller Service being enabled, the 
> service is still disabled on this node, and the ConvertRecord processor is 
> invalid as a result. If you navigate to the Controller Services for the 
> Process Group, though, it shows that the service is enabled. As a result, if 
> the ConvertRecord processor is already running when re-joining, it will show 
> as running but still be invalid on one node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to