Alessio,

Also have in mind that general recommendation is that ZK ensembles use odd
numbers;:

"...Because Zookeeper requires a majority, it is best to use an odd number
of machines..."
[Source:
https://zookeeper.apache.org/doc/r3.1.2/zookeeperAdmin.html#sc_zkMulitServerSetup
]

Cheers



On Fri, Jan 13, 2017 at 12:40 AM, Alessio Palma <
[email protected]> wrote:

> 2 host secured custer.
>
> 2 zookeeper.
> ------------------------------
> *From:* Andre <[email protected]>
> *Sent:* Thursday, January 12, 2017 2:39:23 PM
> *To:* [email protected]
> *Subject:* Re: Cluster is still voting on which Flow is the correct flow
> for the cluster
>
> Alessio,
>
> May I ask you how many zookeeper form your ensemble?
>
> Kind regards
>
> On Fri, Jan 13, 2017 at 12:28 AM, Alessio Palma <
> [email protected]> wrote:
>
>> Hello all,
>>
>> there are 5 minutes of negotiation on the cluster which ends in nothing.
>>
>>
>> These are the logs after the handshake fails:
>>
>>
>> host 1
>>
>>
>> 2017-01-12 13:20:36,448 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator
>> Resetting cluster node statuses from {} to {mid1-t029nifi-2.buongiorno.co
>> m:8080=NodeConnectionStatus[
>> nodeId=mid1-t029nifi-2.buongiorno.com:8080, state=DISCONNECTED,
>> Disconnect Code=Not Has Not Yet Connected to Cluster, Disconnect Reason=Not
>> Has Not Yet Connected to Cluster, u
>> pdateId=1], mid1-t029nifi-1.buongiorno.com:8080=NodeConnectionStatus[nod
>> eId=mid1-t029nifi-1.buongiorno.com:8080, state=CONNECTING, updateId=120]}
>> 2017-01-12 13:20:36,450 ERROR [main] o.a.nifi.controller.StandardFlowService
>> Failed to load flow from cluster due to: 
>> org.apache.nifi.controller.UninheritableFlowException:
>> Fa
>> iled to connect node to cluster because local flow is different than
>> cluster flow.
>> org.apache.nifi.controller.UninheritableFlowException: Failed to connect
>> node to cluster because local flow is different than cluster flow.
>>         at org.apache.nifi.controller.StandardFlowService.loadFromConne
>> ctionResponse(StandardFlowService.java:894)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at 
>> org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:493)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:770)
>> [nifi-jetty-1.1.1.jar:1.1.1]
>>         at org.apache.nifi.NiFi.<init>(NiFi.java:156)
>> [nifi-runtime-1.1.1.jar:1.1.1]
>>         at org.apache.nifi.NiFi.main(NiFi.java:262)
>> [nifi-runtime-1.1.1.jar:1.1.1]
>> Caused by: org.apache.nifi.controller.UninheritableFlowException:
>> Proposed Authorizer is not inheritable by the flow controller because of
>> Authorizer differences: Proposed Aut
>> horizations do not match current Authorizations
>>         at org.apache.nifi.controller.StandardFlowSynchronizer.sync(Sta
>> ndardFlowSynchronizer.java:253) ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at 
>> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1461)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.
>> load(StandardXMLFlowConfigurationDAO.java:83)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at 
>> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:678)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         at org.apache.nifi.controller.StandardFlowService.loadFromConne
>> ctionResponse(StandardFlowService.java:872)
>> ~[nifi-framework-core-1.1.1.jar:1.1.1]
>>         ... 4 common frames omitted
>>
>>
>> Host 2
>>
>> 2017-01-12 13:20:36,900 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator
>> Resetting cluster node statuses from {mid1-t029nifi-2.buongiorno.co
>> m:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-2.buongiorno.com:8080,
>> state=CONNECTING, updateId=122], mid1-t029nifi-1.buongiorno.com
>> :8080=NodeConnectionStatus[nodeId=mid1-t029nifi-1.buongiorno.com:8080,
>> state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow,
>> Disconnect Reason=org.apache.nifi.controller.UninheritableFlowException:
>> Failed to connect node to cluster because local flow is different than
>> cluster flow., updateId=1]} to {mid1-t029nifi-2.buongiorno.co
>> m:8080=NodeConnectionStatus[nodeId=mid1-t029nifi-2.buongiorno.com:8080,
>> state=CONNECTING, updateId=122], mid1-t029nifi-1.buongiorno.com
>> :8080=NodeConnectionStatus[nodeId=mid1-t029nifi-1.buongiorno.com:8080,
>> state=DISCONNECTED, Disconnect Code=Node's Flow did not Match Cluster Flow,
>> Disconnect Reason=org.apache.nifi.controller.UninheritableFlowException:
>> Failed to connect node to cluster because local flow is different than
>> cluster flow., updateId=1]}
>> 2017-01-12 13:20:36,927 INFO [main] o.apache.nifi.controller.FlowController
>> Successfully synchronized controller with proposed flow
>> 2017-01-12 13:20:37,092 INFO [main] org.wali.MinimalLockingWriteAheadLog
>> org.wali.MinimalLockingWriteAheadLog@c42ee90 finished recovering
>> records. Performing Checkpoint to ensure proper state of Partitions before
>> updates
>>
>>
>> What can I check to solve this ?
>>
>
>

Reply via email to