Use linux to start the cluster, not Docker Compose, and encountered some problems

Camunda 8 Topics Discussion & Questions
1

I am trying to use linux to start the cluster, not Docker Compose. But I tried many times and failed to start successfully. The following is my nodeId: 0 configuration information. I first use the command to start nodeId: 0, execute ‘./bin/broker --spring.config.location = file: ./config/broker.yaml’. Then start nodeId: 1.

zeebe:
  broker:
    gateway:
      enable: false

    network:
      host: 0.0.0.0

      data:
      directories: [ data ]

      logSegmentSize: 512MB

      snapshotPeriod: 15m

    cluster:
      nodeId: 0

      partitionsCount: 2

      replicationFactor: 1

      clusterSize: 2
      initialContactPoints : [ 10.151.30.XXX:26502, 10.151.30.XXX:26502 ]
      clusterName: zeebe-cluster

    threads:
      cpuThreadCount: 2
      ioThreadCount: 2
  
    exporters:
      elasticsearch:
        className: io.zeebe.exporter.ElasticsearchExporter
        args:
          url: http://10.151.160.XXX:9200
        
          bulk:
            delay: 5
            size: 1000
        
          index:
            prefix: zeebe-record
            createTemplate: true
       
            command: false
            event: true
            rejection: false
       
            deployment: true
            error: true
            incident: true
            job: true
            jobBatch: false
            message: false
            messageSubscription: false
            variable: true
            variableDocument: true
            workflowInstance: true
            workflowInstanceCreation: false
            workflowInstanceSubscription: false
       
            ignoreVariablesAbove: 32677
2

The logs of the nodes are:
2020-05-08 12:45:26.935 [] [main] INFO io.zeebe.broker.StandaloneBroker - Starting StandaloneBroker v0.23.1 on localhost.localdomain with PID 30240 (/apps/zeebe-broker-0.23.1/lib/zeebe-distribution-0.23.1.jar started by root in /apps/zeebe-broker-0.23.1)
2020-05-08 12:45:26.938 [] [main] INFO io.zeebe.broker.StandaloneBroker - No active profile set, falling back to default profiles: default
2020-05-08 12:45:27.841 [] [main] INFO io.zeebe.broker.StandaloneBroker - Started StandaloneBroker in 1.266 seconds (JVM running for 2.287)
2020-05-08 12:45:27.905 [] [main] INFO io.zeebe.broker.system - Version: 0.23.1
2020-05-08 12:45:27.999 [] [main] INFO io.zeebe.broker.system - Starting broker 0 with configuration {
“network” : {
“host” : “0.0.0.0”,
“portOffset” : 0,
“maxMessageSize” : “4MB”,
“advertisedHost” : “0.0.0.0”,
“commandApi” : {
“host” : “0.0.0.0”,
“port” : 26501,
“advertisedHost” : “0.0.0.0”,
“advertisedPort” : 26501,
“address” : “0.0.0.0:26501”,
“advertisedAddress” : “0.0.0.0:26501”
},
“internalApi” : {
“host” : “0.0.0.0”,
“port” : 26502,
“advertisedHost” : “0.0.0.0”,
“advertisedPort” : 26502,
“address” : “0.0.0.0:26502”,
“advertisedAddress” : “0.0.0.0:26502”
},
“monitoringApi” : {
“host” : “0.0.0.0”,
“port” : 9600,
“advertisedHost” : “0.0.0.0”,
“advertisedPort” : 9600,
“address” : “0.0.0.0:9600”,
“advertisedAddress” : “0.0.0.0:9600”
},
“maxMessageSizeInBytes” : 4194304
},
“cluster” : {
“initialContactPoints” : [ “10.151.30.127:26502”, “10.151.30.128:26502” ],
“partitionIds” : [ 1, 2 ],
“nodeId” : 0,
“partitionsCount” : 2,
“replicationFactor” : 1,
“clusterSize” : 2,
“clusterName” : “zeebe-cluster”,
“gossipFailureTimeout” : 10000,
“gossipInterval” : 250,
“gossipProbeInterval” : 1000
},
“threads” : {
“cpuThreadCount” : 2,
“ioThreadCount” : 2
},
“data” : {
“directories” : [ “/apps/zeebe-broker-0.23.1/data” ],
“logSegmentSize” : “512MB”,
“snapshotPeriod” : “PT15M”,
“logIndexDensity” : 100,
“logSegmentSizeInBytes” : 536870912
},
“exporters” : {
“elasticsearch” : {
“jarPath” : null,
“className” : “io.zeebe.exporter.ElasticsearchExporter”,
“args” : {
“url” : “http://10.151.160.246:9200”,
“bulk” : {
“delay” : 5,
“size” : 1000
},
“index” : {
“prefix” : “zeebe-record”,
“createTemplate” : true,
“command” : false,
“event” : true,
“rejection” : false,
“deployment” : true,
“error” : true,
“incident” : true,
“job” : true,
“jobBatch” : false,
“message” : false,
“messageSubscription” : false,
“variable” : true,
“variableDocument” : true,
“workflowInstance” : true,
“workflowInstanceCreation” : false,
“workflowInstanceSubscription” : false,
“ignoreVariablesAbove” : 32677
}
},
“external” : false
}
},
“gateway” : {
“network” : {
“host” : “0.0.0.0”,
“port” : 26500,
“minKeepAliveInterval” : “PT30S”
},
“cluster” : {
“contactPoint” : “0.0.0.0:26502”,
“requestTimeout” : “PT15S”,
“clusterName” : “zeebe-cluster”,
“memberId” : “gateway”,
“host” : “0.0.0.0”,
“port” : 26502
},
“threads” : {
“managementThreads” : 1
},
“monitoring” : {
“enabled” : false,
“host” : “0.0.0.0”,
“port” : 9600
},
“security” : {
“enabled” : false,
“certificateChainPath” : null,
“privateKeyPath” : null
},
“enable” : false
},
“backpressure” : {
“enabled” : true,
“algorithm” : “VEGAS”
},
“stepTimeout” : “PT5M”
}
2020-05-08 12:45:28.016 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [1/10]: actor scheduler
2020-05-08 12:45:28.021 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [2/10]: membership and replication protocol
2020-05-08 12:45:29.800 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [3/10]: command api transport
2020-05-08 12:45:29.947 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [4/10]: command api handler
2020-05-08 12:45:29.978 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [5/10]: subscription api
2020-05-08 12:45:29.999 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [6/10]: cluster services
2020-05-08 12:45:30.286 [] [raft-server-0-system-partition-1] WARN io.atomix.raft.roles.CandidateRole - RaftServer{system-partition-1}{role=CANDIDATE} - java.net.ConnectException
2020-05-08 12:45:33.941 [] [raft-server-0-system-partition-1] WARN io.atomix.raft.roles.CandidateRole - RaftServer{system-partition-1}{role=CANDIDATE} - java.net.ConnectException

3

I think you should modify your config file like this.

zeebe:
  broker:
    gateway:
      enable: false
    network:
      host: 10.151.30.XXX
2 Likes
4

@lzgabel
I tried like this, but it didn’t work.

5

@wenminglei what is your topology? just one broker and the gateway?

1 Like
6

@salaboy @lzgabel
I am currently only trying to deploy a cluster, so I use two brokers and a gateway.
I found the cause of the problem. An independent gateway must be deployed first. The broker node can be started.
I’m really stupid, hahaha.

1 Like
7