[
https://issues.apache.org/jira/browse/NIFI-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417357#comment-15417357
]
ASF subversion and git services commented on NIFI-2535:
-------------------------------------------------------
Commit 25a2fac453f1a39db9d1f7f759a4fdca80269eca in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=25a2fac ]
NIFI-2535: Do not include properties that are unset in flow fingerprint. This
allows a new property to be added to a processor without affecting the
fingerprint, if the value is never set
This closes #829.
Signed-off-by: Bryan Bende <bbe...@apache.org>
> SSL context service property in Publish/ConsumeKafka is causing clustering
> issue
> ---------------------------------------------------------------------------------
>
> Key: NIFI-2535
> URL: https://issues.apache.org/jira/browse/NIFI-2535
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Haimo Liu
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.0.0
>
>
> NIFI build Aug.9th
> I have a flow with the new kafka processors (publish, consume). it seems like
> the newly added SSL context service property is causing clustering issue (one
> of the nodes cannot join cluster), logs below (tried to copy the flow.xml.gz
> file from node 1 to the other nodes so that they are completely identical,
> doesn't fix the issue):
> 2016-08-09 16:52:38,893 INFO [Reconnect to Cluster]
> o.a.n.c.c.node.NodeClusterCoordinator Resetting cluster node statuses from
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster
> Coordinator], updateId=8],
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33],
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Cluster
> Coordinator], updateId=4]} to
> {localhost:8893=NodeConnectionStatus[state=CONNECTED, roles=[Cluster
> Coordinator], updateId=30],
> localhost:8891=NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33],
> localhost:8892=NodeConnectionStatus[state=CONNECTED, roles=[Primary Node],
> updateId=32]}
> 2016-08-09 16:52:40,071 ERROR [Reconnect to Cluster]
> o.a.nifi.controller.StandardFlowService Handling reconnection request failed
> due to: org.apache.nifi.controller.UninheritableFlowException: Failed 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.loadFromConnectionResponse(StandardFlowService.java:863)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowService.handleReconnectionRequest(StandardFlowService.java:589)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowService.access$300(StandardFlowService.java:97)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowService$2.run(StandardFlowService.java:401)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
> Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed
> configuration is not inheritable by the flow controller because of flow
> differences: Found difference in Flows:
> Local Fingerprint:
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEssl.context.serviceNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000-0000-00004224fe88org.apache.nifi.pr
> Cluster Fingerprint:
> he.nifi.processors.kafka.pubsub.Partitioners$RoundRobinPartitionersasl.kerberos.service.nameNO_VALUEtopicWARNINGsuccess04015ca0-0156-1000-0000-00004224fe88org.apache.nifi.processors.standard.GenerateF
> at
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:240)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1429)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:81)
> ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:668)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:839)
> [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> ... 4 common frames omitted
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster]
> o.a.n.c.c.node.NodeClusterCoordinator localhost:8891 requested disconnection
> from cluster due to org.apache.nifi.controller.UninheritableFlowException:
> Failed to connect node to cluster because local flow is different than
> cluster flow.
> 2016-08-09 16:52:40,071 INFO [Reconnect to Cluster]
> o.a.n.c.c.node.NodeClusterCoordinator Status of localhost:8891 changed from
> NodeConnectionStatus[state=CONNECTING, roles=[], updateId=33] to
> NodeConnectionStatus[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.,
> roles=[], updateId=33]
> 2016-08-09 16:52:40,072 INFO [Reconnect to Cluster]
> o.a.n.c.c.node.NodeClusterCoordinator Determined that Cluster Coordinator is
> located at localhost:9093
> 2016-08-09 16:52:40,073 ERROR [Reconnect to Cluster]
> o.a.n.c.c.node.NodeClusterCoordinator Event Reported for localhost:8891 --
> Node disconnected from cluster due to
> org.apache.nifi.controller.UninheritableFlowException: Failed to connect node
> to cluster because local flow is different than cluster flow.
> 2016-08-09 16:52:44,043 WARN [Remote Process Group
> 294a8b19-0156-1000-0000-000048fbc6d8: http://172.26.32.220:8080/nifi
> Thread-1] o.a.n.remote.StandardRemoteProcessGroup Unable to connect to
> RemoteProcessGroup[http://172.26.32.220:8080/nifi] due to
> org.apache.http.conn.HttpHostConnectException: Connect to localhost:18080
> [localhost/127.0.0.1] failed: Connection refused
> 2016-08-09 16:52:46,508 INFO [Site-to-Site Worker Thread-3]
> o.a.nifi.remote.SocketRemoteSiteListener Received connection from
> localhost/127.0.0.1, User DN: null
> 2016-08-09 16:52:46,521 INFO [Site-to-Site Worker Thread-3]
> o.a.nifi.remote.SocketRemoteSiteListener Successfully negotiated
> ServerProtocol SocketFlowFileProtocol Version 6 with
> Peer[url=nifi://localhost:59767]
> 2016-08-09 16:52:46,670 INFO [Site-to-Site Worker Thread-4]
> o.a.nifi.remote.SocketRemoteSiteListener Received connection from
> localhost/127.0.0.1, User DN: null
> 2016-08-09 16:52:46,683 INFO [Site-to-Site Worker Thread-4]
> o.a.nifi.remote.SocketRemoteSiteListener Successfully negotiated
> ServerProtocol SocketFlowFileProtocol Version 6 with
> Peer[url=nifi://localhost:59770]
> 2016-08-09 16:52:46,774 INFO [Site-to-Site Worker Thread-4]
> o.a.n.r.p.s.SocketFlowFileServerProtocol Sending list of 2 peers back to
> client Peer[url=nifi://localhost:59770]
> 2016-08-09 16:52:46,774 INFO [Site-to-Site Worker Thread-3]
> o.a.n.r.p.s.SocketFlowFileServerProtocol Sending list of 2 peers back to
> client Peer[url=nifi://localhost:59767]
> 2016-08-09 16:52:46,784 INFO [NiFi Site-to-Site Connection Pool Maintenance]
> o.apache.nifi.remote.client.PeerSelector
> org.apache.nifi.remote.client.PeerSelector@3694296d Successfully refreshed
> Peer Status; remote instance consists of 2 peers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
