You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Sunil Yadav (Jira)" <ji...@apache.org> on 2022/01/07 08:27:00 UTC

[jira] [Commented] (NIFI-9551) nifi cluster in kubernetes

    [ https://issues.apache.org/jira/browse/NIFI-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470420#comment-17470420 ] 

Sunil Yadav commented on NIFI-9551:
-----------------------------------

Error in UI

!image-2022-01-07-13-56-03-673.png!

> nifi cluster in kubernetes
> --------------------------
>
>                 Key: NIFI-9551
>                 URL: https://issues.apache.org/jira/browse/NIFI-9551
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Sunil Yadav
>            Priority: Major
>         Attachments: image-2022-01-07-13-56-03-673.png
>
>
> Im trying to setup a simple 2-node nifi cluster in kubernetes and am having a problem with any configuration beyond 1 node.All of the nodes start up and eventually 1 is elected the primary and the other one come up as "Connected".
> The problem arises whenever I attempt to actually start building a flow and adding processors. The message I get whenever I try to add a processor to an empty flow looks like this:
> 2022-01-07 08:21:13,748 INFO [Replicate Request Thread-1] o.a.n.c.c.h.r.ThreadPoolRequestReplicator Received a status of 409 from 0.0.0.0:8080 for request POST /nifi-api/process-groups/333e44d7-017e-1000-692a-1e0e40286af9/processors when performing first stage of two-stage commit. The action will not occur. Node explanation: Transaction 38c6bf71-20af-405d-a490-fdc5eb77d570 is already in progress.
> 2022-01-07 08:21:13,748 DEBUG [NiFi Web Server-203] o.a.nifi.web.api.ApplicationResource Took a total of 113 millis to Replicate Request POST http://localhost:8080/nifi-api/process-groups/333e44d7-017e-1000-692a-1e0e40286af9/processors for Request with no ID
> Details: 
> * Nifi 1.12.1 configured as a StatefulSet (replicas = 2) in kubernetes
> * Using external zookeeper running on K8s. correctly and has no errors. 
> Relevant nifi.properties
> {{# cluster node properties (only configure for cluster nodes) #}}
> {{nifi.cluster.is.node=true}}
> {{nifi.cluster.node.address=nifi-0.nifi.default.svc.cluster.local}}
> {{nifi.cluster.node.protocol.port=8082}}
> {{nifi.cluster.node.protocol.max.threads=20}}
> {{nifi.cluster.node.event.history.size=25}}
> {{nifi.cluster.node.connection.timeout=5 sec}}
> {{nifi.cluster.node.read.timeout=5 sec}}
> {{nifi.cluster.node.max.concurrent.requests=100}}
> {{nifi.cluster.firewall.file=}}
> {{nifi.cluster.flow.election.max.wait.time=20 sec}}
> {{nifi.cluster.flow.election.max.candidates=1}}
> {{# web properties #}}
> {{#############################################}}
> {{nifi.web.http.host=0.0.0.0}}
> {{nifi.web.http.port=8080}}
> {{nifi.web.http.network.interface.default=}}
>  
> {{####################}}
> {{# State Management #}}
> {{####################}}
> {{nifi.state.management.configuration.file=./conf/state-management.xml}}
> {{# The ID of the local state provider}}
> {{nifi.state.management.provider.local=local-provider}}
> {{# The ID of the cluster-wide state provider. This will be ignored if NiFi is not clustered but must be populated if running in a cluster.}}
> {{nifi.state.management.provider.cluster=zk-provider}}
> {{# Specifies whether or not this instance of NiFi should run an embedded ZooKeeper server}}
> {{nifi.state.management.embedded.zookeeper.start=false}}
> {{# Properties file that provides the ZooKeeper properties to use if <nifi.state.management.embedded.zookeeper.start> is set to true}}
> {{nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties}}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)