Re: Build error on nifi-site-to-site-client

[Mark Bean]

Short answer: Java 11 build succeeded after upgrading to Java 11.0.7.

For anyone else that may find themselves in a similar situation, here are
some details. I used homebrew and jenv on MacOS to install adoptopenjdk.
Previously, I had openjdk 11.0.2 installed. I'm not sure if the root cause
was version 11.0.2 or the fact that it was OpenJDK versus AdoptOpenJDK.

Here is the process:

$ brew tap adoptopenjdk/openjdk
$ brew cask install adoptopenjdk11
$ /usr/libexec/java_home -V
Matching Java Virtual Machines (3):
11.0.7, x86_64: "AdoptOpenJDK 11"
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
11.0.2, x86_64: "OpenJDK 11.0.2"
/Library/Java/JavaVirtualMachines/openjdk-11.0.2.jdk/Contents/Home
1.8.0_241, x86_64: "Java SE 8"
/Library/Java/JavaVirtualMachines/jdk1.8.0_241.jdk/Contents/Home

$ jenv add
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
$ jenv global 11.0.7

I emptied my local maven repository and ran 'mvn clean install'
(single-threaded) to prevent any other possible issues. The build succeeded.

Thanks,
Mark


On Wed, Jun 10, 2020 at 1:47 PM Andy LoPresto  wrote:

> Hi Mark,
>
> I just worked on these areas and those tests were passing successfully for
> me on Mac OS X 10.15.5 with OpenJDK 11.0.6 and Maven 3.6.3. They also
> passed on the GitHub Actions builds using Java 11. Do you have any custom
> DNS configurations or certificates imported in your OS keystore which might
> be affecting this?
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jun 10, 2020, at 10:22 AM, Mark Bean  wrote:
> >
> > I am attempting to build master (01e42dfb) using Java 11, but getting
> test
> > failures. It builds fine with Java 8. There are two failing tests with
> > stack traces shown below.
> >
> > Anyone else experiencing similar issues? Or, are there suggestions on
> what
> > might be the problem?
> >
> > MacOS10.15.5
> > openjdk-11.0.2
> > Maven 3.6.3
> >
> > [ERROR]
> > testSendSuccessHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
> > Time elapsed: 0.092 s  <<< ERROR!
> >
> > java.io.IOException: Failed to complete transaction with Peer[url=
> > https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
> > https://localhost:62046/nifi-api, TransferDirection=SEND,
> > State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
> > https://localhost:62046/nifi-api] when expecting a TransactionFinished
> > Indicator. It is unknown whether or not the peer successfully
> > received/processed the data. javax.net.ssl.SSLPeerUnverifiedException:
> peer
> > not authenticated
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> >
> > Caused by: java.io.IOException: [Url=https://localhost:62046/nifi-api,
> > TransferDirection=SEND, State=TRANSACTION_CONFIRMED] Failed to receive a
> > response from Peer[url=https://localhost:62046/nifi-api] when expecting
> a
> > TransactionFinished Indicator. It is unknown whether or not the peer
> > successfully received/processed the data.
> > javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> >
> > Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not
> authenticated
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> >
> >
> > [ERROR]
> > testSendLargeFileHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
> > Time elapsed: 0.068 s  <<< ERROR!
> >
> > java.io.IOException: Failed to complete transaction with Peer[url=
> > https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
> > https://localhost:62046/nifi-api, TransferDirection=SEND,
> > State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
> > https://localhost:62046/nifi-api] when expecting a TransactionFinished
> > Indicator. It is unknown whether or not the peer successfully
> > received/processed the data. javax.net.ssl.SSLPeerUnverifiedException:
> peer
> > not authenticated
> >
> > at
> >
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> >
> > at

Re: Build error on nifi-site-to-site-client

[Andy LoPresto]

Hi Mark,

I just worked on these areas and those tests were passing successfully for me 
on Mac OS X 10.15.5 with OpenJDK 11.0.6 and Maven 3.6.3. They also passed on 
the GitHub Actions builds using Java 11. Do you have any custom DNS 
configurations or certificates imported in your OS keystore which might be 
affecting this?

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jun 10, 2020, at 10:22 AM, Mark Bean  wrote:
> 
> I am attempting to build master (01e42dfb) using Java 11, but getting test
> failures. It builds fine with Java 8. There are two failing tests with
> stack traces shown below.
> 
> Anyone else experiencing similar issues? Or, are there suggestions on what
> might be the problem?
> 
> MacOS10.15.5
> openjdk-11.0.2
> Maven 3.6.3
> 
> [ERROR]
> testSendSuccessHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
> Time elapsed: 0.092 s  <<< ERROR!
> 
> java.io.IOException: Failed to complete transaction with Peer[url=
> https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
> https://localhost:62046/nifi-api, TransferDirection=SEND,
> State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
> https://localhost:62046/nifi-api] when expecting a TransactionFinished
> Indicator. It is unknown whether or not the peer successfully
> received/processed the data. javax.net.ssl.SSLPeerUnverifiedException: peer
> not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> 
> Caused by: java.io.IOException: [Url=https://localhost:62046/nifi-api,
> TransferDirection=SEND, State=TRANSACTION_CONFIRMED] Failed to receive a
> response from Peer[url=https://localhost:62046/nifi-api] when expecting a
> TransactionFinished Indicator. It is unknown whether or not the peer
> successfully received/processed the data.
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> 
> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)
> 
> 
> [ERROR]
> testSendLargeFileHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
> Time elapsed: 0.068 s  <<< ERROR!
> 
> java.io.IOException: Failed to complete transaction with Peer[url=
> https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
> https://localhost:62046/nifi-api, TransferDirection=SEND,
> State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
> https://localhost:62046/nifi-api] when expecting a TransactionFinished
> Indicator. It is unknown whether or not the peer successfully
> received/processed the data. javax.net.ssl.SSLPeerUnverifiedException: peer
> not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFileHTTPS(TestHttpClient.java:1014)
> 
> Caused by: java.io.IOException: [Url=https://localhost:62046/nifi-api,
> TransferDirection=SEND, State=TRANSACTION_CONFIRMED] Failed to receive a
> response from Peer[url=https://localhost:62046/nifi-api] when expecting a
> TransactionFinished Indicator. It is unknown whether or not the peer
> successfully received/processed the data.
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFileHTTPS(TestHttpClient.java:1014)
> 
> Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)
> 
> at
> org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)
> 
> at
> 

Build error on nifi-site-to-site-client

[Mark Bean]

I am attempting to build master (01e42dfb) using Java 11, but getting test
failures. It builds fine with Java 8. There are two failing tests with
stack traces shown below.

Anyone else experiencing similar issues? Or, are there suggestions on what
might be the problem?

MacOS10.15.5
openjdk-11.0.2
Maven 3.6.3

[ERROR]
testSendSuccessHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
 Time elapsed: 0.092 s  <<< ERROR!

java.io.IOException: Failed to complete transaction with Peer[url=
https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
https://localhost:62046/nifi-api, TransferDirection=SEND,
State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
https://localhost:62046/nifi-api] when expecting a TransactionFinished
Indicator. It is unknown whether or not the peer successfully
received/processed the data. javax.net.ssl.SSLPeerUnverifiedException: peer
not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)

Caused by: java.io.IOException: [Url=https://localhost:62046/nifi-api,
TransferDirection=SEND, State=TRANSACTION_CONFIRMED] Failed to receive a
response from Peer[url=https://localhost:62046/nifi-api] when expecting a
TransactionFinished Indicator. It is unknown whether or not the peer
successfully received/processed the data.
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)

Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSend(TestHttpClient.java:789)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendSuccessHTTPS(TestHttpClient.java:905)


[ERROR]
testSendLargeFileHTTPS(org.apache.nifi.remote.client.http.TestHttpClient)
 Time elapsed: 0.068 s  <<< ERROR!

java.io.IOException: Failed to complete transaction with Peer[url=
https://localhost:62046/nifi-api] due to java.io.IOException: [Url=
https://localhost:62046/nifi-api, TransferDirection=SEND,
State=TRANSACTION_CONFIRMED] Failed to receive a response from Peer[url=
https://localhost:62046/nifi-api] when expecting a TransactionFinished
Indicator. It is unknown whether or not the peer successfully
received/processed the data. javax.net.ssl.SSLPeerUnverifiedException: peer
not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFileHTTPS(TestHttpClient.java:1014)

Caused by: java.io.IOException: [Url=https://localhost:62046/nifi-api,
TransferDirection=SEND, State=TRANSACTION_CONFIRMED] Failed to receive a
response from Peer[url=https://localhost:62046/nifi-api] when expecting a
TransactionFinished Indicator. It is unknown whether or not the peer
successfully received/processed the data.
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFileHTTPS(TestHttpClient.java:1014)

Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendIgnoreProxyError(TestHttpClient.java:931)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFile(TestHttpClient.java:944)

at
org.apache.nifi.remote.client.http.TestHttpClient.testSendLargeFileHTTPS(TestHttpClient.java:1014)

Re: Potential Problems on Discarding Return Values

[Andy LoPresto]

Hi Adam,

The mailing list strips a lot of attachments, your PDF included. The best way I 
have found to share this kind of information with the community is to put it on 
the Apache NiFi Wiki [1] or post a GitHub Gist [2], etc. Thanks. 

[1] https://cwiki.apache.org/confluence/display/NIFI/Apache+NiFi 

[2] https://gist.github.com/ 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jun 10, 2020, at 3:33 AM, Adam Hunyadi  
> wrote:
> 
> Hi,
> 
> Sorry, I did not realize, that this confluence page might not be available 
> for some devs.
> 
> Attached the content as pdf.
> 
> Thanks,
> Adam
> 
> On 2020. 06. 10. 12:11, Adam Hunyadi wrote:
>> Hi,
>> 
>> Upon checking some behaviours in NiFi with Tamas Palfy, we have found that 
>> function signatures like this can be a frequent source of error:
>> 
>> public FlowFile penalize(FlowFile flowFile) { ... }
>> 
>> I documented the issue here:
>> 
>> https://cloudera.atlassian.net/wiki/spaces/ENG/pages/610534373/Discarding+Return+Values+in+NiFi
>>  
>> 
>> It would be nice if a Java dev with some spare time could look more into the 
>> issue and share their findings.
>> 
>> Cheers,
>> Adam
>> 

Re: NiFi module with curator error

[Mark Payne]

Vasily,

The code that deals with Curator is in nifi-framework-core in the 
CuratorLeaderElectionManager.

I do think it makes sense though to look at the 
"-Dcurator-log-only-first-connection-issue-as-error-level=true” option first. 
If that doesn’t resolve the issue, it may make sense to look at fixing the 
issue in Curator itself, rather than trying to put something into NiFi to work 
around the issue. Seems if NiFi is running into this issue, others likely are 
as well.

Thanks
-Mark

> On Jun 10, 2020, at 9:45 AM, Vasily Makarov 
>  wrote:
> 
> Hi all!
> 
>  1.  Which NiFi module can throw such an error? nifi-framework-core? This 
> exception is due that not all zookeeper nodes defined in logs are up and 
> running.
>  2.  2. Can this connection request to the curator/zookeper be found in java 
> code in some particular line of code? Or is it like in the configuration side?
> 
> 2020-01-16 08:58:28,767 ERROR [Curator-Framework-0] 
> o.a.c.f.imps.CuratorFrameworkImpl Background retry gave up
> org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = 
> ConnectionLoss
>at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:972)
>at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:943)
>at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:66)
>at 
> org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:346)
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>at java.lang.Thread.run(Thread.java:748)
> 
> (I'm working on https://jira.apache.org/jira/browse/NIFI-7035   - right now 
> my idea is to implement custom turbo filter in logbase to limit this spam of 
> CuratorFrameworkImpl logs. Any help would be appreciated)

NiFi module with curator error

[Vasily Makarov]

Hi all!

  1.  Which NiFi module can throw such an error? nifi-framework-core? This 
exception is due that not all zookeeper nodes defined in logs are up and 
running.
  2.  2. Can this connection request to the curator/zookeper be found in java 
code in some particular line of code? Or is it like in the configuration side?

2020-01-16 08:58:28,767 ERROR [Curator-Framework-0] 
o.a.c.f.imps.CuratorFrameworkImpl Background retry gave up
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = 
ConnectionLoss
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:972)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:943)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:66)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:346)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

(I'm working on https://jira.apache.org/jira/browse/NIFI-7035   - right now my 
idea is to implement custom turbo filter in logbase to limit this spam of 
CuratorFrameworkImpl logs. Any help would be appreciated)

Re: Potential Problems on Discarding Return Values

[Adam Hunyadi]

Hi,

Sorry, I did not realize, that this confluence page might not be 
available for some devs.


Attached the content as pdf.

Thanks,
Adam

On 2020. 06. 10. 12:11, Adam Hunyadi wrote:


Hi,

Upon checking some behaviours in NiFi with Tamas Palfy, we have found 
that function signatures like this can be a frequent source of error:


|public FlowFile penalize(FlowFile flowFile) { ... }|

I documented the issue here:

https://cloudera.atlassian.net/wiki/spaces/ENG/pages/610534373/Discarding+Return+Values+in+NiFi

It would be nice if a Java dev with some spare time could look more 
into the issue and share their findings.


Cheers,
Adam

Potential Problems on Discarding Return Values

[Adam Hunyadi]

Hi,

Upon checking some behaviours in NiFi with Tamas Palfy, we have found 
that function signatures like this can be a frequent source of error:


|public FlowFile penalize(FlowFile flowFile) { ... }|

I documented the issue here:

https://cloudera.atlassian.net/wiki/spaces/ENG/pages/610534373/Discarding+Return+Values+in+NiFi

It would be nice if a Java dev with some spare time could look more into 
the issue and share their findings.


Cheers,
Adam

Re: How to enable processors after changing a controller service automatically?

[Stefan Kok]

Also you may want to have a  look at:

https://community.cloudera.com/t5/Support-Questions/Start-Controller-Service-via-NiFi-REST-API/td-p/218165


On Wed, 2020-06-10 at 09:40 +0800, l...@china-inv.cn wrote:
> Hi, All,
> 
> I'm using NiFi 1.6.0. I need to change a setting of a contoller
> service, 
> NiFi stopped all the processors that reference this service then
> disable 
> the service before I could make changes.
> After I made the change and re-enable the service, I found that the 
> processors were NOT
> re-enabled automatically.
> 
> I have to enable these processors manually. Since there are thousands
> of 
> such processors
> this operation is very time-consuming. 
> 
> Does anyone know how to tell NiFi to start those processors
> automatically?
> 
> Thanks 
> 
> 
> 
> 陆伯鹰
> 中国投资有限责任公司信息技术部
> 电话：+86 (0)10 84096521
> 传真：+86 (0)10 64086851 
> 北京市东城区朝阳门北大街1号新保利大厦8层 100010
> 网站：www.china-inv.cn 
>  
> 
> 
> 
> 
>  
> 本邮件内容包含保密信息。如阁下并非拟发送的收件人，请您不要阅读、保存、对外
> 披露或复制本邮件的任何内容，或者打开本邮件的任何附件。请即回复邮件告知发件
> 人，并立刻将该邮件及其附件从您的电脑系统中全部删除，不胜感激。
> 
>  
> This email message may contain confidential and/or privileged
> information. 
> If you are not the intended recipient, please do not read, save,
> forward, 
> disclose or copy the contents of this email or open any file attached
> to 
> this email. We will be grateful if you could advise the sender
> immediately 
> by replying this email, and delete this email and any attachment or
> links 
> to this email completely and immediately from your computer system. 
> 
> 
> 

Re: How to enable processors after changing a controller service automatically?

[Stefan Kok]

Not sure if you tried this:

On the "Enable Controller Service " screen there is a dropdown labelled
"scope". The default setting is "Service only" click and select
"Service and referencing components" then click enable.

Hope this helps.
Stefan

On Wed, 2020-06-10 at 09:40 +0800, l...@china-inv.cn wrote:
> Hi, All,
> 
> I'm using NiFi 1.6.0. I need to change a setting of a contoller
> service, 
> NiFi stopped all the processors that reference this service then
> disable 
> the service before I could make changes.
> After I made the change and re-enable the service, I found that the 
> processors were NOT
> re-enabled automatically.
> 
> I have to enable these processors manually. Since there are thousands
> of 
> such processors
> this operation is very time-consuming. 
> 
> Does anyone know how to tell NiFi to start those processors
> automatically?
> 
> Thanks 
> 
> 
> 
> 陆伯鹰
> 中国投资有限责任公司信息技术部
> 电话：+86 (0)10 84096521
> 传真：+86 (0)10 64086851 
> 北京市东城区朝阳门北大街1号新保利大厦8层 100010
> 网站：www.china-inv.cn 
>  
> 
> 
> 
> 
>  
> 本邮件内容包含保密信息。如阁下并非拟发送的收件人，请您不要阅读、保存、对外
> 披露或复制本邮件的任何内容，或者打开本邮件的任何附件。请即回复邮件告知发件
> 人，并立刻将该邮件及其附件从您的电脑系统中全部删除，不胜感激。
> 
>  
> This email message may contain confidential and/or privileged
> information. 
> If you are not the intended recipient, please do not read, save,
> forward, 
> disclose or copy the contents of this email or open any file attached
> to 
> this email. We will be grateful if you could advise the sender
> immediately 
> by replying this email, and delete this email and any attachment or
> links 
> to this email completely and immediately from your computer system. 
> 
> 
>