# Issue with multi-node setup

**URL:** <https://forum.weaviate.io/t/issue-with-multi-node-setup/2074>\
**Category:** Support\
**Created:** [April 20, 2024, 2:35pm UTC](https://forum.weaviate.io/t/issue-with-multi-node-setup/2074 "2024-04-20T14:35:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vamsi](https://avatars.discourse-cdn.com/v4/letter/v/b38774/32.png) [@vamsi](https://forum.weaviate.io/u/vamsi)\
**Post date:** [April 20, 2024, 2:35pm UTC](https://forum.weaviate.io/t/issue-with-multi-node-setup/2074/1 "2024-04-20T14:35:32Z")

</div>

### Description

We have a 5-node setup hosted through docker compose.

The issue I am facing is:

All the nodes are not added to cluster when I do `docker compose up -d`. There will always be at least 1 node missing (checking `/v1/nodes`) from the cluster even though all the containers are up and running.

If I start each node one after the other then they are being added to the cluster immediately.

```auto
docker compose up weaviate-node-1 -d
docker compose up weaviate-node-2 -d
docker compose up weaviate-node-3 -d
docker compose up weaviate-node-4 -d
docker compose up weaviate-node-5 -d

```

Adding `healthcheck` on first node, `depends_on` on all nodes did not resolve this issue.

If any container restarts for some reason it is not joining the cluster again as well.

Any help is appreciated in this regard.

### Server Setup Information

- Weaviate Server Version: 1.24.1
- Deployment Method: docker
- Multi Node? Number of Running Nodes: 5
- Client Language and Version:

### Any additional Information

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [April 20, 2024, 3:08pm UTC](https://forum.weaviate.io/t/issue-with-multi-node-setup/2074/2 "2024-04-20T15:08:21Z")

</div>

Hi @vamsi !

Do you see any outstanding logs on the node that has not joined the cluster?

Fortunately, in our next 1.25 version we’ll be delivering [raft consensus](https://raft.github.io/) along with many other improvements that will greatly improve a cluster resilience.

here for more info:

> <https://github.com/weaviate/weaviate/issues/4280>
>
> \## tl;dr
> The outcome of #3515. All cluster meta data including schema informati…on will be managed with RAFT in the future. This increases fault-tolerance and fixes "schema out of sync" errors once and for all.
> 
> \## Issues addressed by RAFT
> 
> \* \`schema out of sync\` startup errors: RAFT will keep the schema in sync.
> \* \`concurrent transaction\` error on schema change: The current schema tx cannot handle concurrency, the RAFT setup will.
> 
> \## Migration Journey
> The migration journey will be designed in a way that no extra steps are necessary. A regular rolling update will handle the migration automatically.
> 
> \## Downgrading after upgrading
> After upgrading to the RAFT-based version (likely v1.25), downgrading directly will no longer be supported. For those wanting to go back to an older version, a backup-and-restore is required.

Thanks!