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

Oleg Zhurakousky commented on NIFI-2160:
----------------------------------------

Brandon

Correct me if I am wrong, but based on your explanation you're using some 
custom code (". . .we use a custom domain specific langauge that can reference 
a controller service. . .") to reference the CS. That means NiFi is not aware 
of this relationship(s). 
I do understand that this is a problem within your current approach, but if the 
above is correct I wonder if this is really a bug in NiFi (let alone 
"Critical"). IMHO, NiFi has a very specific way of defining the relationships 
between components and if any relationships exist outside of NiFi core 
relationship model, then don't you think it would be the responsibility of your 
custom DSL to enable the CS if it is disabled?

That said, I think the real issue is simply with the fact that CS (regardless 
of it's relationship to anything) was in ENABLED state when NiFi was shut down 
and is DISABLED upon restart of NiFi. That is indeed a bug. Do you agree? If 
so, I'll be more then glad to make it a priority, otherwise let's make sure 
we're are addressing the real issue (whatever that may be). 

> Enabled ControllerServices disabled on restart
> ----------------------------------------------
>
>                 Key: NIFI-2160
>                 URL: https://issues.apache.org/jira/browse/NIFI-2160
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Brandon DeVries
>            Priority: Critical
>             Fix For: 0.7.0
>
>
> As a result of the fix for NIFI-2032, previously enabled ControllerServices 
> become disabled after a restart if they are not referenced by another 
> component.  However, we use a custom domain specific langauge that can 
> reference a controller service from a query defined as a custom processor's 
> property.  This means that we use a number of controller service that are 
> only used in this way (i.e. are never directly referred to by another 
> component).  Upon restart, these are now disabled causing issues with our 
> flows.
> I have not yet stepped through the new enableControllerServices() \[1\] 
> method to figure out exactly where the issue is coming from, but I wanted to 
> get the ticket out there and on the radar, as this breaks backwards 
> compatibility on a feature we heavily rely on.
> \[1\] 
> https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceProvider.java#L301-336



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to