Skip to content
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

Replication Hangs in Kubernetes and Docker #1219

Closed
jtsmedley opened this issue Aug 25, 2023 · 1 comment
Closed

Replication Hangs in Kubernetes and Docker #1219

jtsmedley opened this issue Aug 25, 2023 · 1 comment
Assignees
Labels
bug Something isn't working fixed
Milestone

Comments

@jtsmedley
Copy link

ArcadeDB Version:

23.7.1

OS and JDK Version:

All OS and Versions

Expected behavior

Cluster nodes should be able to be added as replicas and be able to retrieve the cluster configuration from /api/v1/server?mode=cluster

Actual behavior

Cluster Replica Nodes in Docker and Kubernetes fail to lookup the proper leader IP address on response to /api/v1/server?mode=cluster and causes replication to hang on the container until rebooted

Steps to reproduce

Run docker-compose up on the below docker-compose.yaml. Open the Studio UI on any of the Replicas and navigate to the cluster overview page. Any SQL function ran before going to the cluster replica page will work, but then after going to the cluster overview page on any of the replicas you cause the replication process to hang and it does not resume.

`services:
arcadedb0:
container_name: arcadedb0
hostname: arcadedb0
image: arcadedata/arcadedb:latest
command:
- bin/server.sh
- -Darcadedb.dumpConfigAtStartup=true
- -Darcadedb.server.name=arcadedb0
- -Darcadedb.server.databaseDirectory=/mnt/data0/databases
- -Darcadedb.ha.enabled=true
- -Darcadedb.ha.replicationIncomingHost=0.0.0.0
- -Darcadedb.ha.serverList=arcadedb0:2424
- -Darcadedb.server.rootPassword=playwithdata
ports:
- "2480:2480"
- "2424:2424"

arcadedb1:
container_name: arcadedb1
hostname: arcadedb1
image: arcadedata/arcadedb:latest
command:
- bin/server.sh
- -Darcadedb.dumpConfigAtStartup=true
- -Darcadedb.server.name=arcadedb1
- -Darcadedb.server.databaseDirectory=/mnt/data0/databases
- -Darcadedb.ha.enabled=true
- -Darcadedb.ha.replicationIncomingHost=0.0.0.0
- -Darcadedb.ha.replicationIncomingPorts=2425-2435
- -Darcadedb.ha.serverList=arcadedb0:2424
- -Darcadedb.server.rootPassword=playwithdata
ports:
- "2481:2480"
- "2425:2425"

arcadedb2:
container_name: arcadedb2
hostname: arcadedb2
image: arcadedata/arcadedb:latest
command:
- bin/server.sh
- -Darcadedb.dumpConfigAtStartup=true
- -Darcadedb.server.name=arcadedb2
- -Darcadedb.server.databaseDirectory=/mnt/data0/databases
- -Darcadedb.ha.enabled=true
- -Darcadedb.ha.replicationIncomingHost=0.0.0.0
- -Darcadedb.ha.replicationIncomingPorts=2426-2436
- -Darcadedb.ha.serverList=arcadedb0:2424
- -Darcadedb.server.rootPassword=playwithdata
ports:
- "2482:2480"
- "2426:2426"`

@lvca lvca self-assigned this Sep 20, 2023
@lvca lvca added the bug Something isn't working label Sep 20, 2023
@lvca
Copy link
Contributor

lvca commented Oct 31, 2023

This issue seems resolved by 54fae76

@lvca lvca closed this as completed Oct 31, 2023
@lvca lvca added this to the 23.10.1 milestone Oct 31, 2023
@lvca lvca added the fixed label Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed
Projects
None yet
Development

No branches or pull requests

2 participants