Exception while restarting the Nifi Cluster

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Exception while restarting the Nifi Cluster

Rahul Dahiya
Hi Team,


I am getting below exception while trying to restart the NiFi nodes :


java.lang.Exception: Unable to load flow due to: java.io.IOException: org.apache.nifi.cluster.ConnectionException: Failed to connect node to cluster because local flow controller partially updated.  Administrator should disconnect node and review flow for corruption.
    at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:783) ~[nifi-jetty-0.6.1.jar:0.6.1]
    at org.apache.nifi.NiFi.<init>(NiFi.java:137) [nifi-runtime-0.6.1.jar:0.6.1]
    at org.apache.nifi.NiFi.main(NiFi.java:227) [nifi-runtime-0.6.1.jar:0.6.1]



Based on the following link :

https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%3CBAY172-W19DF8C4EDE001FC6B8CA0ECE6B0@...%3E


it seems that the issue could be because of trailing while space /  incorrect entries in the following properties files


nifi.sensitive.props.key
nifi.sensitive.props.algorithm
nifi.sensitive.props.provider


I've checked these properties files on all the nodes and they are exactly the same on all nodes with no trailing white space.


Can someone please help on what could be the root cause of this problem and how can it be resolved .


Also I don't want to clean the nifi working directories (I know it will work fine on cleaning the directories). Thanks in advance for the help.


Regards,

Rahul
Reply | Threaded
Open this post in threaded view
|

Re: Exception while restarting the Nifi Cluster

dale.chang13
Rahul Dahiya wrote
Hi Team,


I am getting below exception while trying to restart the NiFi nodes :


java.lang.Exception: Unable to load flow due to: java.io.IOException: org.apache.nifi.cluster.ConnectionException: Failed to connect node to cluster because local flow controller partially updated.  Administrator should disconnect node and review flow for corruption.
    at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:783) ~[nifi-jetty-0.6.1.jar:0.6.1]
    at org.apache.nifi.NiFi.<init>(NiFi.java:137) [nifi-runtime-0.6.1.jar:0.6.1]
    at org.apache.nifi.NiFi.main(NiFi.java:227) [nifi-runtime-0.6.1.jar:0.6.1]



Based on the following link :

<a href="https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%">https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%[hidden email]%3E


it seems that the issue could be because of trailing while space /  incorrect entries in the following properties files


nifi.sensitive.props.key
nifi.sensitive.props.algorithm
nifi.sensitive.props.provider


I've checked these properties files on all the nodes and they are exactly the same on all nodes with no trailing white space.


Can someone please help on what could be the root cause of this problem and how can it be resolved .


Also I don't want to clean the nifi working directories (I know it will work fine on cleaning the directories). Thanks in advance for the help.


Regards,

Rahul
Could you give us the rest of the stack trace? It should contain more information that would help us further diagnose your problem
Reply | Threaded
Open this post in threaded view
|

RE: Exception while restarting the Nifi Cluster

Sourav Gulati
Hi Nifi Team,

We analyzed the issue and found that it is because of custom processor library missing in lib.

Steps to reproduce:
1. Create nar of custom processor and add it to the lib.
2. Start nifi and create a flow using that custom processor.
3. Stop nifi and remove the nar of custom processor
4. Start nifi

While starting it throws this exception. I think instead of Nifi instance not getting started and throwing error in such case. It should start and that particular flow remains disabled which is using this library.

Regards,
Sourav Gulati

-----Original Message-----
From: dale.chang13 [mailto:[hidden email]]
Sent: Wednesday, May 11, 2016 5:24 PM
To: [hidden email]
Subject: Re: Exception while restarting the Nifi Cluster

Rahul Dahiya wrote

> Hi Team,
>
>
> I am getting below exception while trying to restart the NiFi nodes :
>
>
> java.lang.Exception: Unable to load flow due to: java.io.IOException:
> org.apache.nifi.cluster.ConnectionException: Failed to connect node to
> cluster because local flow controller partially updated.
> Administrator should disconnect node and review flow for corruption.
>     at
> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:783)
> ~[nifi-jetty-0.6.1.jar:0.6.1]
>     at org.apache.nifi.NiFi.
> <init>
> (NiFi.java:137) [nifi-runtime-0.6.1.jar:0.6.1]
>     at org.apache.nifi.NiFi.main(NiFi.java:227)
> [nifi-runtime-0.6.1.jar:0.6.1]
>
>
>
> Based on the following link :
>
> <a href="https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%">https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%

> 3CBAY172-W19DF8C4EDE001FC6B8CA0ECE6B0@

> %3E
>
>
> it seems that the issue could be because of trailing while space /
> incorrect entries in the following properties files
>
>
> nifi.sensitive.props.key
> nifi.sensitive.props.algorithm
> nifi.sensitive.props.provider
>
>
> I've checked these properties files on all the nodes and they are
> exactly the same on all nodes with no trailing white space.
>
>
> Can someone please help on what could be the root cause of this
> problem and how can it be resolved .
>
>
> Also I don't want to clean the nifi working directories (I know it
> will work fine on cleaning the directories). Thanks in advance for the help.
>
>
> Regards,
>
> Rahul

Could you give us the rest of the stack trace? It should contain more information that would help us further diagnose your problem



--
View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Exception-while-restarting-the-Nifi-Cluster-tp10135p10137.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

________________________________






NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.
Reply | Threaded
Open this post in threaded view
|

Re: Exception while restarting the Nifi Cluster

Mark Payne
Sourav,

This certainly is something that we can improve upon, and there is actually already a
ticket created to handle this [1]. The idea is that we want to startup with some sort of
placeholder there so that the user is able to replace the processor with whatever makes
sense.

Thanks
-Mark


[1] https://issues.apache.org/jira/browse/NIFI-1052 <https://issues.apache.org/jira/browse/NIFI-1052>



> On May 12, 2016, at 1:40 AM, Sourav Gulati <[hidden email]> wrote:
>
> Hi Nifi Team,
>
> We analyzed the issue and found that it is because of custom processor library missing in lib.
>
> Steps to reproduce:
> 1. Create nar of custom processor and add it to the lib.
> 2. Start nifi and create a flow using that custom processor.
> 3. Stop nifi and remove the nar of custom processor
> 4. Start nifi
>
> While starting it throws this exception. I think instead of Nifi instance not getting started and throwing error in such case. It should start and that particular flow remains disabled which is using this library.
>
> Regards,
> Sourav Gulati
>
> -----Original Message-----
> From: dale.chang13 [mailto:[hidden email]]
> Sent: Wednesday, May 11, 2016 5:24 PM
> To: [hidden email]
> Subject: Re: Exception while restarting the Nifi Cluster
>
> Rahul Dahiya wrote
>> Hi Team,
>>
>>
>> I am getting below exception while trying to restart the NiFi nodes :
>>
>>
>> java.lang.Exception: Unable to load flow due to: java.io.IOException:
>> org.apache.nifi.cluster.ConnectionException: Failed to connect node to
>> cluster because local flow controller partially updated.
>> Administrator should disconnect node and review flow for corruption.
>>    at
>> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:783)
>> ~[nifi-jetty-0.6.1.jar:0.6.1]
>>    at org.apache.nifi.NiFi.
>> <init>
>> (NiFi.java:137) [nifi-runtime-0.6.1.jar:0.6.1]
>>    at org.apache.nifi.NiFi.main(NiFi.java:227)
>> [nifi-runtime-0.6.1.jar:0.6.1]
>>
>>
>>
>> Based on the following link :
>>
>> <a href="https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%">https://mail-archives.apache.org/mod_mbox/nifi-dev/201508.mbox/%
>
>> 3CBAY172-W19DF8C4EDE001FC6B8CA0ECE6B0@
>
>> %3E
>>
>>
>> it seems that the issue could be because of trailing while space /
>> incorrect entries in the following properties files
>>
>>
>> nifi.sensitive.props.key
>> nifi.sensitive.props.algorithm
>> nifi.sensitive.props.provider
>>
>>
>> I've checked these properties files on all the nodes and they are
>> exactly the same on all nodes with no trailing white space.
>>
>>
>> Can someone please help on what could be the root cause of this
>> problem and how can it be resolved .
>>
>>
>> Also I don't want to clean the nifi working directories (I know it
>> will work fine on cleaning the directories). Thanks in advance for the help.
>>
>>
>> Regards,
>>
>> Rahul
>
> Could you give us the rest of the stack trace? It should contain more information that would help us further diagnose your problem
>
>
>
> --
> View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Exception-while-restarting-the-Nifi-Cluster-tp10135p10137.html
> Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
>
> ________________________________
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference.