-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zeebe cluster when node 0 fail cluster fail #18583
Comments
Hey @ahmedbeledy sorry but it is not really clear what your issue is, could you please reformat your issue description and elaborate what you're observing vs. expecting and what you have tried so far? |
hello @Zelldon Node 0 If either Node 1 or Node 2 fails, the system continues to work as expected. Can you help me understand why this behavior is occurring and how to fix it? Thank you. |
Thanks @ahmedbeledy Could you answer the following questions:
In general I would recommend to have this kind of discussion in the forum https://forum.camunda.io/ and if you found a clear bug/issue, open an issue here. |
1- local setup i not use kind or docker i download release and run it from bin |
Could you post the logs from the different brokers and gateway please and also tell me to which gateway you connect. What is the port and IP? Maybe you connect to an embedded gateway from the broker 0 ? 🤔 |
gateway config gateway: |
@Zelldon This issue seems ZDP specific. I'm removing it from our board, please re-add if you think we should take care of something here. |
Hey @ahmedbeledy sorry but the provided screenshots are not really useful. I would need to see more than that. Furthermore, see my questions above #18583 (comment) that haven't been covered yet. I will close this issue as this is mostly investigating and troubleshooting and no actual issue to work on. Please raise your problem in the forum https://forum.camunda.io/ Make sure to provide as much as possible information, like configurations, logs (upload them directly, no screenshots), explain what your expectation is and your observation, etc. |
problem
I have a basic problem with my setup. I have 4 servers: one gateway and three nodes acting as brokers. The nodes are named as follows:
Node 0
Node 1
Node 2
Here is the issue:
If either Node 1 or Node 2 fails, the system continues to work as expected.
However, if Node 0 fails, the entire system stops working.
This issue does not occur when using Docker. The problem only happens on the local machine setup. Additionally, I've attached my configuration files at the bottom of this message.
Can you help me understand why this behavior is occurring and how to fix it?
Environment:
OS: Windows 10
Zeebe Version:8.5.1
installed : locally 4 machines one gateway and other node broker
configration :
gatway config
zeebe:
gateway:
network:
host: 192.168.8.115
port: 26500
cluster:
host: 192.168.8.115
port: 26502
initialContactPoints: [192.168.8.114:26502 , 192.168.8.110:26502 , 192.168.8.105:26502]
# initialContactPoints: [192.168.8.114:26502 ]
security:
enabled: false
multiTenancy:
enabled: false
nodes config
first node
zeebe:
broker:
gateway:
enable: false
zeebe:
broker:
gateway:
enable: false
zeebe:
broker:
gateway:
enable: false
i try in docker and its works fine my docker file
version: "2"
networks:
zeebe_network:
driver: bridge
services:
gateway:
restart: always
container_name: gateway
image: camunda/zeebe:${ZEEBE_VERSION}
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=node0:26502
- ZEEBE_GATEWAY_CLUSTER_PORT=26502
- ZEEBE_GATEWAY_CLUSTER_HOST=gateway
ports:
- "26500:26500"
networks:
- zeebe_network
node0:
container_name: zeebe_broker_1
image: camunda/zeebe:${ZEEBE_VERSION}
environment:
- ZEEBE_LOG_LEVEL=debug
- ZEEBE_BROKER_CLUSTER_NODEID=0
- ZEEBE_BROKER_CLUSTER_PARTITIONSCOUNT=2
- ZEEBE_BROKER_CLUSTER_REPLICATIONFACTOR=3
- ZEEBE_BROKER_CLUSTER_CLUSTERSIZE=3
- ZEEBE_BROKER_CLUSTER_INITIALCONTACTPOINTS=node0:26502,node1:26502,node2:26502
node1:
container_name: zeebe_broker_2
image: camunda/zeebe:${ZEEBE_VERSION}
environment:
- 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=node0:26502,node1:26502,node2:26502
networks:
- zeebe_network
depends_on:
- node0
node2:
container_name: zeebe_broker_3
image: camunda/zeebe:${ZEEBE_VERSION}
environment:
- ZEEBE_LOG_LEVEL=debug
- ZEEBE_BROKER_CLUSTER_NODEID=2
- ZEEBE_BROKER_CLUSTER_PARTITIONSCOUNT=2
- ZEEBE_BROKER_CLUSTER_REPLICATIONFACTOR=3
- ZEEBE_BROKER_CLUSTER_CLUSTERSIZE=3
- ZEEBE_BROKER_CLUSTER_INITIALCONTACTPOINTS=node0:26502,node1:26502,node2:26502
networks:
- zeebe_network
depends_on:
- node0
i try contactpoint like docker and not work
The text was updated successfully, but these errors were encountered: