search

cetic / helm-nifi

Helm Chart for Apache Nifi
Apache License 2.0
215 stars 225 forks source link

[cetic/nifi] Cannot connect more than one node to cluster #254

Closed congtranminh closed 2 years ago

congtranminh commented 2 years ago

Describe the bug I used helm to install nifi cluster via the command

helm install my-release --set replicaCount=3 --set properties.isNode=true --set zookeeper.replicaCount=1 --set zookeeper.enabled=true cetic/nifi

Here is the pod running after I ran the command image

But when I go through the nifi cluster config, I only see 1 node image

Version of Helm, Kubernetes and the Nifi chart:

What happened: Only one node running on the cluster

What you expected to happen: 3 nodes must be listed on the nifi cluster

Hope you guys can help me out. Thanks :)

wknickless commented 2 years ago

@congtranminh Thank you for providing such a succinct helm command. When I ran it I saw these errors in the app-log container log:

2022-05-16 18:50:40,877 INFO [main] o.a.n.c.p.AbstractNodeProtocolSender Cluster Coordinator is located at my-release-nifi-1.my-release-nifi-headless.default.svc.cluster.local:6007. Will send Cluster Connection Request to this address
2022-05-16 18:50:42,015 WARN [main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed marshalling 'CONNECTION_REQUEST' protocol message due to: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors

This happens when the NiFi cluster doesn't have its PKI certificates set up. That's what PR #218 can help provide via cert-manager.

congtranminh commented 2 years ago

Thank you @wknickless. I'll follow your PR. Right now, I made some customs from the source to disable the SSL and the cluster connect successfully.