Zeebe cluster setup

mayank · August 17, 2020, 12:49pm

Hi, I am trying to set up a Zeebe cluster on three ec2 instances but getting error
zeebe_broker_2 | 2020-08-17 12:34:54.187 [] [raft-server-1-system-partition-1] WARN io.atomix.raft.roles.FollowerRole - RaftServer{system-partition-1}{role=FOLLOWER} - java.net.ConnectException

ports are open on the machine.
I tried multiple ways to setup like

gateway and broker on all three instances
only brokers and gateway separate
but getting similar errors

Can someone please here help and share a sample docker-compose file to be used on three servers?

salaboy · August 18, 2020, 8:34am

@mayank a docker compose file used on three servers? I am not aware of anything like that… you might want to look at Kubernetes for doing a multi host cluster. I wouldn’t use docker compose for that.

ruozhixian · August 19, 2020, 3:19am

Note the IP and port.
In docker-compose.yml:

services:
  zeebe:
	image: camunda/zeebe:0.23.5
	environment:
	  - ZEEiBE_LOG_LEVEL=debug
	  - ZEEBE_BROKER_NETWORK_HOST=0.0.0.0
	  - ZEEBE_BROKER_GATEWAY_CLUSTER_HOST=0.0.0.0
	  - ZEEBE_BROKER_NETWORK_COMMANDAPI_HOST=13.13.13.34        # the local host IP
	  - ZEEBE_BROKER_NETWORK_INTERNALAPI_HOST=13.13.13.34
	ports:
	  - "26500:26500"
	  - "26501:26501"
	  - "26502:26502"
	  - "9600:9600"

salaboy · August 19, 2020, 8:16am

I’ve never done a setup like that… so I am not sure if I can help here… if someone else have done that before… please advise…

mayank · August 19, 2020, 10:00am

Hi ruozhixian,

Thank you for your help, I am struggling with what should be all other env variables I should mention,
is it the complete list of env variable?

Zelldon · August 19, 2020, 10:07am

Hey @mayank

you can take a look at the config in the doc. For each configuration the env variable is also specified.
https://docs.zeebe.io/appendix/broker-config-template.html#standalone-broker-with-embedded-gateway

Greets
Chris

mayank · August 19, 2020, 12:49pm

Hi Zelldon,

I have config like below on all three ec2 instances
version: “2”

networks:
zeebe_network:
driver: bridge

services:
node1:
container_name: zeebe_broker_2
image: camunda/zeebe:0.23.1
environment:
- ZEEBE_HOST=127.0.0.1
- ZEEBE_LOG_LEVEL=debug
- ZEEBE_BROKER_CLUSTER_NODEID=1
- ZEEBE_BROKER_CLUSTER_PARTITIONSCOUNT=2
- ZEEBE_BROKER_CLUSTER_REPLICATIONFACTOR=3
- ZEEBE_BROKER_CLUSTER_CLUSTERSIZE=3
- ZEEBE_BROKER_CLUSTER_INITIALCONTACTPOINTS=127.0.0.1:26502,node_1_ip:26502,node_2_ip:26502
ports:
- “26502:26502”
- “26501:26501”
- “26500:26500”
# volumes:
# - ./zeebe.cfg.toml:/usr/local/zeebe/conf/zeebe.cfg.toml
networks:
- zeebe_network

But I am getting the RaftServer{system-partition-1}{role=FOLLOWER} - java.net.ConnectException on all three servers

Zelldon · August 19, 2020, 2:27pm

Hey @mayank

could you please post the cfg which is printed by the brokers on startup?

Greets
Chris

mayank · August 20, 2020, 9:35am

Hi Zelldon,

Find the config below
Broker config
{
zeebe_broker_3 | “network” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “portOffset” : 0,
zeebe_broker_3 | “maxMessageSize” : “4MB”,
zeebe_broker_3 | “advertisedHost” : “127.0.0.1”,
zeebe_broker_3 | “commandApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26501,
zeebe_broker_3 | “advertisedHost” : “127.0.0.1”,
zeebe_broker_3 | “advertisedPort” : 26501,
zeebe_broker_3 | “address” : “127.0.0.1:26501”,
zeebe_broker_3 | “advertisedAddress” : “127.0.0.1:26501”
zeebe_broker_3 | },
zeebe_broker_3 | “internalApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26502,
zeebe_broker_3 | “advertisedHost” : “127.0.0.1”,
zeebe_broker_3 | “advertisedPort” : 26502,
zeebe_broker_3 | “address” : “127.0.0.1:26502”,
zeebe_broker_3 | “advertisedAddress” : “127.0.0.1:26502”
zeebe_broker_3 | },
zeebe_broker_3 | “monitoringApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 9600,
zeebe_broker_3 | “advertisedHost” : “127.0.0.1”,
zeebe_broker_3 | “advertisedPort” : 9600,
zeebe_broker_3 | “address” : “127.0.0.1:9600”,
zeebe_broker_3 | “advertisedAddress” : “127.0.0.1:9600”
zeebe_broker_3 | },
zeebe_broker_3 | “maxMessageSizeInBytes” : 4194304
zeebe_broker_3 | },
zeebe_broker_3 | “cluster” : {
zeebe_broker_3 | “initialContactPoints” : [ “127.0.0.1:26502”, “172.31.34.170:26502”, “172.31.44.55:26502” ],
zeebe_broker_3 | “partitionIds” : [ 1, 2 ],
zeebe_broker_3 | “nodeId” : 2,
zeebe_broker_3 | “partitionsCount” : 2,
zeebe_broker_3 | “replicationFactor” : 3,
zeebe_broker_3 | “clusterSize” : 3,
zeebe_broker_3 | “clusterName” : “zeebe-cluster”,
zeebe_broker_3 | “gossipFailureTimeout” : 10000,
zeebe_broker_3 | “gossipInterval” : 250,
zeebe_broker_3 | “gossipProbeInterval” : 1000
zeebe_broker_3 | },
zeebe_broker_3 | “threads” : {
zeebe_broker_3 | “cpuThreadCount” : 2,
zeebe_broker_3 | “ioThreadCount” : 2
zeebe_broker_3 | },
zeebe_broker_3 | “data” : {
zeebe_broker_3 | “directories” : [ “/usr/local/zeebe/data” ],
zeebe_broker_3 | “logSegmentSize” : “512MB”,
zeebe_broker_3 | “snapshotPeriod” : “PT15M”,
zeebe_broker_3 | “logIndexDensity” : 100,
zeebe_broker_3 | “logSegmentSizeInBytes” : 536870912
zeebe_broker_3 | },
zeebe_broker_3 | “exporters” : { },
zeebe_broker_3 | “gateway” : {
zeebe_broker_3 | “network” : {
zeebe_broker_3 | “host” : “0.0.0.0”,
zeebe_broker_3 | “port” : 26500,
zeebe_broker_3 | “minKeepAliveInterval” : “PT30S”
zeebe_broker_3 | },
zeebe_broker_3 | “cluster” : {
zeebe_broker_3 | “contactPoint” : “127.0.0.1:26502”,
zeebe_broker_3 | “requestTimeout” : “PT15S”,
zeebe_broker_3 | “clusterName” : “zeebe-cluster”,
zeebe_broker_3 | “memberId” : “gateway”,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26502
zeebe_broker_3 | },
zeebe_broker_3 | “threads” : {
zeebe_broker_3 | “managementThreads” : 1
zeebe_broker_3 | },
zeebe_broker_3 | “monitoring” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 9600
zeebe_broker_3 | },
zeebe_broker_3 | “security” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “certificateChainPath” : null,
zeebe_broker_3 | “privateKeyPath” : null
zeebe_broker_3 | },
zeebe_broker_3 | “enable” : true
zeebe_broker_3 | },
zeebe_broker_3 | “backpressure” : {
zeebe_broker_3 | “enabled” : true,
zeebe_broker_3 | “algorithm” : “VEGAS”
zeebe_broker_3 | },
zeebe_broker_3 | “stepTimeout” : “PT5M”
zeebe_broker_3 | }

Gateway config
{
zeebe_broker_3 | “network” : {
zeebe_broker_3 | “host” : “0.0.0.0”,
zeebe_broker_3 | “port” : 26500,
zeebe_broker_3 | “minKeepAliveInterval” : “PT30S”
zeebe_broker_3 | },
zeebe_broker_3 | “cluster” : {
zeebe_broker_3 | “contactPoint” : “127.0.0.1:26502”,
zeebe_broker_3 | “requestTimeout” : “PT15S”,
zeebe_broker_3 | “clusterName” : “zeebe-cluster”,
zeebe_broker_3 | “memberId” : “gateway”,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26502
zeebe_broker_3 | },
zeebe_broker_3 | “threads” : {
zeebe_broker_3 | “managementThreads” : 1
zeebe_broker_3 | },
zeebe_broker_3 | “monitoring” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 9600
zeebe_broker_3 | },
zeebe_broker_3 | “security” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “certificateChainPath” : null,
zeebe_broker_3 | “privateKeyPath” : null
zeebe_broker_3 | },
zeebe_broker_3 | “enable” : true
zeebe_broker_3 | }

When I check the cluster status I get something like below
./zbctl --insecure status
Cluster size: 0
Partitions count: 0
Replication factor: 0
Gateway version: 0.23.1
Brokers:

Zelldon · August 20, 2020, 9:46am

I think the issue is that your advertised host is set to localhost. You need to set the host to an ip or dns name reachable by the other brokers.

You can take a look how we do it in the helm charts
https://github.com/zeebe-io/zeebe-cluster-helm/blob/master/zeebe-cluster/templates/configmap.yaml#L12

Or see a related discussion and solution

github.com/camunda/zeebe

ZEEBE_ADVERTISED_HOST doesn't work

opened 02:57PM - 30 Oct 19 UTC

closed 04:07PM - 30 Oct 19 UTC

IcyEagle

kind/bug

Hi there! I'm deploying a Zeebe cluster in k8s with 3 nodes. We use Istio (ha…ve Envoy installed within a pod), that's why the **advertised host** feature is required to make it work. Here is my zeebe.cfg.toml: ``` # For more information about this configuration visit: [threads] cpuThreadCount = 1 [network] host = "0.0.0.0" [gateway.monitoring] enabled = true [...exporters configuration omitted...] ``` My startup.sh script ``` #!/bin/bash -xeu configFile=/usr/local/zeebe/conf/zeebe.cfg.toml export ZEEBE_NODE_ID="${HOSTNAME##*-}" export ZEEBE_ADVERTISED_HOST=$(hostname -f) # We need to specify all brokers as contact points for partition healing to work correctly # https://github.com/zeebe-io/zeebe/issues/2684 ZEEBE_CONTACT_POINTS=${HOSTNAME::-1}0.$(hostname -d):26502 for (( i=1; i<$ZEEBE_CLUSTER_SIZE; i++ )) do ZEEBE_CONTACT_POINTS="${ZEEBE_CONTACT_POINTS},${HOSTNAME::-1}$i.$(hostname -d):26502" done export ZEEBE_CONTACT_POINTS="${ZEEBE_CONTACT_POINTS}" exec /usr/local/zeebe/bin/broker ``` Here is what I have: ``` ➜ ~ k exec -it zeebe-cluster-0 -c zeebe-cluster ./bin/zbctl status -- --insecure Cluster size: 3 Partitions count: 3 Replication factor: 3 Brokers: Broker 0 - 0.0.0.0:26501 Broker 1 - 0.0.0.0:26501 Broker 2 - 0.0.0.0:26501 ``` My statefulset descriptor: ``` apiVersion: apps/v1 kind: StatefulSet metadata: name: {{ include "zeebe-cluster.fullname" . }} namespace: {{ include "zeebe-cluster.namespace" . }} labels: {{ include "zeebe-cluster.labels" . | indent 4 }} spec: replicas: {{ .Values.replicaCount }} selector: matchLabels: app.kubernetes.io/name: {{ include "zeebe-cluster.name" . }} app.kubernetes.io/instance: {{ .Release.Name }} serviceName: {{ include "zeebe-cluster.fullname" . }} updateStrategy: type: RollingUpdate podManagementPolicy: Parallel template: metadata: annotations: prometheus.io/port: "9600" prometheus.io/scrape: "true" prometheus.io/path: "/metrics" labels: app.kubernetes.io/name: {{ include "zeebe-cluster.name" . }} app.kubernetes.io/instance: {{ .Release.Name }} json_logs: "true" spec: containers: - name: {{ .Chart.Name }} image: "{{ .Values.image.url }}:{{ .Values.version }}" imagePullPolicy: {{ .Values.image.pullPolicy }} env: - name: ZEEBE_LOG_LEVEL value: info - name: ZEEBE_PARTITIONS_COUNT value: "3" - name: ZEEBE_CLUSTER_SIZE value: "3" - name: ZEEBE_REPLICATION_FACTOR value: "3" - name: JAVA_TOOL_OPTIONS value: {{- toYaml .Values.JavaOpts | nindent 16}} ports: - containerPort: {{ .Values.service.http.port }} name: http - containerPort: {{ .Values.service.gateway.port }} name: gateway - containerPort: {{ .Values.service.command.port }} name: command - containerPort: {{ .Values.service.internal.port }} name: internal readinessProbe: httpGet: path: {{ .Values.service.http.healthcheckPath }} port: http initialDelaySeconds: 60 periodSeconds: 50 livenessProbe: httpGet: path: {{ .Values.service.http.healthcheckPath }} port: http initialDelaySeconds: 120 periodSeconds: 30 failureThreshold: 10 resources: {{- toYaml .Values.resources | nindent 12 }} volumeMounts: - name: config mountPath: /usr/local/zeebe/conf/zeebe.cfg.toml subPath: zeebe.cfg.toml - name: config mountPath: /usr/local/zeebe/conf/log4j2.xml subPath: log4j2.xml - name: config mountPath: /usr/local/bin/startup.sh subPath: startup.sh - name: data mountPath: /usr/local/zeebe/data volumes: - name: config configMap: name: {{ include "zeebe-cluster.fullname" . }} defaultMode: 0744 volumeClaimTemplates: - metadata: name: data spec: accessModes: [ "ReadWriteOnce" ] resources: requests: storage: 5Gi ``` I use your image `comunda/zeebe:0.21.1` It worth noting it works "better" when I bind 26501 port to `hostname -f` (default) instead of `0.0.0.0`, but this way cluster can be assembled **only** when I flush all persistent volumes. Maybe, it can help.

Hope that helps

Greets
Chris

mayank · August 20, 2020, 10:12am

Hi Zelldon,

Thanks a lot!!
The raft conn error is gone. Let me check the other things of the cluster.

mayank · August 21, 2020, 7:55am

Hi @Zelldon @salaboy

Disturbing you again, need one more help,
I am trying to start the standalone gate but it is also facing connection issue
2020-08-21 07:34:14.042 [] [atomix-0] WARN io.atomix.primitive.partition.impl.DefaultPartitionGroupMembershipService - Failed to locate management group via bootstrap nodes. Please ensure partition groups are configured either locally or remotely and the node is able to reach partition group members.
gateway | 2020-08-21 07:34:15.047 [] [atomix-partition-group-membership-service-0] WARN io.atomix.primitive.partition.impl.DefaultPartitionGroupMembershipService - Failed to locate management group via bootstrap nodes. Please ensure partition groups are configured either locally or remotely and the node is able to reach partition group members.
gateway | 2020-08-21 07:34:16.048 [] [atomix-partition-group-membership-service-0] WARN io.atomix.primitive.partition.impl.DefaultPartitionGroupMembershipService - Failed to locate management group via bootstrap nodes. Please ensure partition groups are configured either locally or remotely and the node is able to reach partition group members.

Below is config from logs
{
gateway | “network” : {
gateway | “host” : “127.0.0.0”,
gateway | “port” : 26500,
gateway | “minKeepAliveInterval” : “PT30S”
gateway | },
gateway | “cluster” : {
gateway | “contactPoint” : “172.31.34.170:26502,172.31.32.27:26502,172.31.44.55:26502”,
gateway | “requestTimeout” : “PT15S”,
gateway | “clusterName” : “zeebe-cluster”,
gateway | “memberId” : “gateway”,
gateway | “host” : “172.31.32.27”,
gateway | “port” : 26502
gateway | },
gateway | “threads” : {
gateway | “managementThreads” : 1
gateway | },
gateway | “monitoring” : {
gateway | “enabled” : false,
gateway | “host” : “0.0.0.0”,
gateway | “port” : 9600
gateway | },
gateway | “security” : {
gateway | “enabled” : false,
gateway | “certificateChainPath” : null,
gateway | “privateKeyPath” : null
gateway | }
gateway | }

any idea?

mayank · August 24, 2020, 5:27am

Hi, @Zelldon @salaboy @ruozhixian
Please help on the above question.

thanks,
Mayank

ruozhixian · August 24, 2020, 5:47am

Hey, @mayank

for the standalone gateway contactPoint , one node is enough to be the initial contact point.

just for example, the complete docker-compose.yml:

version: "2"

services:
  gateway:
	restart: always
	container_name: gateway
	image: camunda/zeebe:0.23.4
	environment:
	  - ZEEBE_LOG_LEVEL=debug
	  - ZEEBE_STANDALONE_GATEWAY=true
	  - ZEEBE_GATEWAY_NETWORK_HOST=0.0.0.0
	  - ZEEBE_GATEWAY_NETWORK_PORT=26500
	  - ZEEBE_GATEWAY_CLUSTER_CONTACTPOINT=13.13.13.33:26502           # the initial contact node host ip
	  - ZEEBE_GATEWAY_CLUSTER_PORT=26502
	  - ZEEBE_GATEWAY_CLUSTER_HOST=13.13.13.38               # the gateway host ip
	  - ZEEBE_GATEWAY_SECURITY_ENABLED=false
	  - ZEEBE_GATEWAY_LONGPOLLING_ENABLED=true
	ports:
	  - "26500:26500"
	  - "26502:26502"

mayank · August 24, 2020, 5:56am

thanks @ruozhixian let me try this.

mayank · August 24, 2020, 8:27am

@ruozhixian @Zelldon still getting the same issue on gateway
2020-08-24 08:21:44.654 [] [atomix-0] WARN io.atomix.primitive.partition.impl.DefaultPartitionGroupMembershipService - Failed to locate management group via bootstrap nodes. Please ensure partition groups are configured either locally or remotely and the node is able to reach partition group members.
gateway | 2020-08-24 08:21:45.661 [] [atomix-partition-group-membership-service-0] WARN io.atomix.primitive.partition.impl.DefaultPartitionGroupMembershipService - Failed to locate management group via bootstrap nodes. Please ensure partition groups are configured either locally or remotely and the node is able to reach partition group members.

Gateway config is as below
{
gateway | “network” : {
gateway | “host” : “127.0.0.0”,
gateway | “port” : 26500,
gateway | “minKeepAliveInterval” : “PT30S”
gateway | },
gateway | “cluster” : {
gateway | “contactPoint” : “172.31.32.27:26502”,
gateway | “requestTimeout” : “PT15S”,
gateway | “clusterName” : “zeebe-cluster”,
gateway | “memberId” : “gateway”,
gateway | “host” : “172.31.32.27”,
gateway | “port” : 26502
gateway | },
gateway | “threads” : {
gateway | “managementThreads” : 1
gateway | },
gateway | “monitoring” : {
gateway | “enabled” : false,
gateway | “host” : “0.0.0.0”,
gateway | “port” : 9600
gateway | },
gateway | “security” : {
gateway | “enabled” : false,
gateway | “certificateChainPath” : null,
gateway | “privateKeyPath” : null
gateway | }
gateway | }

and broker config is as below
{
zeebe_broker_3 | “network” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “portOffset” : 0,
zeebe_broker_3 | “maxMessageSize” : “4MB”,
zeebe_broker_3 | “advertisedHost” : “172.31.32.27”,
zeebe_broker_3 | “commandApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26501,
zeebe_broker_3 | “advertisedHost” : “172.31.32.27”,
zeebe_broker_3 | “advertisedPort” : 26501,
zeebe_broker_3 | “address” : “127.0.0.1:26501”,
zeebe_broker_3 | “advertisedAddress” : “172.31.32.27:26501”
zeebe_broker_3 | },
zeebe_broker_3 | “internalApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26502,
zeebe_broker_3 | “advertisedHost” : “172.31.32.27”,
zeebe_broker_3 | “advertisedPort” : 26502,
zeebe_broker_3 | “address” : “127.0.0.1:26502”,
zeebe_broker_3 | “advertisedAddress” : “172.31.32.27:26502”
zeebe_broker_3 | },
zeebe_broker_3 | “monitoringApi” : {
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 9600,
zeebe_broker_3 | “advertisedHost” : “172.31.32.27”,
zeebe_broker_3 | “advertisedPort” : 9600,
zeebe_broker_3 | “address” : “127.0.0.1:9600”,
zeebe_broker_3 | “advertisedAddress” : “172.31.32.27:9600”
zeebe_broker_3 | },
zeebe_broker_3 | “maxMessageSizeInBytes” : 4194304
zeebe_broker_3 | },
zeebe_broker_3 | “cluster” : {
zeebe_broker_3 | “initialContactPoints” : [ “127.0.0.1:26502”, “172.31.34.170:26502”, “172.31.44.55:26502” ],
zeebe_broker_3 | “partitionIds” : [ 1, 2 ],
zeebe_broker_3 | “nodeId” : 2,
zeebe_broker_3 | “partitionsCount” : 2,
zeebe_broker_3 | “replicationFactor” : 3,
zeebe_broker_3 | “clusterSize” : 3,
zeebe_broker_3 | “clusterName” : “zeebe-cluster”,
zeebe_broker_3 | “gossipFailureTimeout” : 10000,
zeebe_broker_3 | “gossipInterval” : 250,
zeebe_broker_3 | “gossipProbeInterval” : 1000
zeebe_broker_3 | },
zeebe_broker_3 | “threads” : {
zeebe_broker_3 | “cpuThreadCount” : 2,
zeebe_broker_3 | “ioThreadCount” : 2
zeebe_broker_3 | },
zeebe_broker_3 | “data” : {
zeebe_broker_3 | “directories” : [ “/usr/local/zeebe/data” ],
zeebe_broker_3 | “logSegmentSize” : “512MB”,
zeebe_broker_3 | “snapshotPeriod” : “PT15M”,
zeebe_broker_3 | “logIndexDensity” : 100,
zeebe_broker_3 | “logSegmentSizeInBytes” : 536870912
zeebe_broker_3 | },
zeebe_broker_3 | “exporters” : { },
zeebe_broker_3 | “gateway” : {
zeebe_broker_3 | “network” : {
zeebe_broker_3 | “host” : “0.0.0.0”,
zeebe_broker_3 | “port” : 26500,
zeebe_broker_3 | “minKeepAliveInterval” : “PT30S”
zeebe_broker_3 | },
zeebe_broker_3 | “cluster” : {
zeebe_broker_3 | “contactPoint” : “127.0.0.1:26502”,
zeebe_broker_3 | “requestTimeout” : “PT15S”,
zeebe_broker_3 | “clusterName” : “zeebe-cluster”,
zeebe_broker_3 | “memberId” : “gateway”,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 26502
zeebe_broker_3 | },
zeebe_broker_3 | “threads” : {
zeebe_broker_3 | “managementThreads” : 1
zeebe_broker_3 | },
zeebe_broker_3 | “monitoring” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “host” : “127.0.0.1”,
zeebe_broker_3 | “port” : 9600
zeebe_broker_3 | },
zeebe_broker_3 | “security” : {
zeebe_broker_3 | “enabled” : false,
zeebe_broker_3 | “certificateChainPath” : null,
zeebe_broker_3 | “privateKeyPath” : null
zeebe_broker_3 | },
zeebe_broker_3 | “enable” : false
zeebe_broker_3 | },
zeebe_broker_3 | “backpressure” : {
zeebe_broker_3 | “enabled” : true,
zeebe_broker_3 | “algorithm” : “VEGAS”
zeebe_broker_3 | },
zeebe_broker_3 | “stepTimeout” : “PT5M”
zeebe_broker_3 | }

Mohit646 · October 9, 2020, 11:43am

Hi @mayank ,

How do you resolved I am still facing the issue ?

zeebe_node1.1.nzp489et1ivk@node1 | 2020-10-09 13:21:00.361 [] [raft-server-1-system-partition-1] WARN io.atomix.raft.roles.FollowerRole - RaftServer{system-partition-1}{role=FOLLOWER} - java.net.ConnectException

Mohit646 · October 12, 2020, 7:33am

Anyone can help on this?

system · January 31, 2024, 10:11am