# Weaviate scalability

**URL:** <https://forum.weaviate.io/t/weaviate-scalability/1208>\
**Category:** Support\
**Created:** [January 11, 2024, 10:01am UTC](https://forum.weaviate.io/t/weaviate-scalability/1208 "2024-01-11T10:01:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lina\_7amed](https://avatars.discourse-cdn.com/v4/letter/l/dc4da7/32.png) [@lina\_7amed](https://forum.weaviate.io/u/lina_7amed)\
**Post date:** [January 11, 2024, 10:01am UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/1 "2024-01-11T10:01:33Z")

</div>

Hello,

I have weaviate deployment on K8s (Production environment), and now i need to scale it to 3 replicas.

when i tried that, i found only one container is working at a time and the other ones disconnects

is there any missing configuration i need to add to make it work?

Appreciate your help!

---

<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:** [January 15, 2024, 5:48pm UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/2 "2024-01-15T17:48:35Z")

</div>

Hi @lina_7amed ! Welcome to our community 🙂

Can you provide us with some logs and reproducible steps for that?

when you increase the replica number in the helm chart, it should work as expected.

---

<div class="post-metadata">

**Author:** ![lina\_7amed](https://avatars.discourse-cdn.com/v4/letter/l/dc4da7/32.png) [@lina\_7amed](https://forum.weaviate.io/u/lina_7amed)\
**Post date:** [January 16, 2024, 7:20pm UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/3 "2024-01-16T19:20:51Z")

</div>

Hello, Thanks for your reply

Actually i’m not using the helm chart

This is my environment variables used in the deployment:

QUERY\_DEFAULTS\_LIMIT: ‘25’  
AUTHENTICATION\_ANONYMOUS\_ACCESS\_ENABLED: ‘false’  
PERSISTENCE\_DATA\_PATH: /var/lib/weaviate  
DEFAULT\_VECTORIZER\_MODULE: none  
CLUSTER\_HOSTNAME: node1  
AUTHENTICATION\_APIKEY\_ENABLED: ‘true’  
AUTHENTICATION\_APIKEY\_ALLOWED\_KEYS:  
AUTHENTICATION\_APIKEY\_USERS:  
AUTHORIZATION\_ADMINLIST\_ENABLED: ‘true’  
AUTHORIZATION\_ADMINLIST\_USERS:

and this is the image i’m using “semitechnologies/weaviate:1.18.4”

do i miss any configuration here?

Thanks

---

<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:** [January 17, 2024, 1:58pm UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/4 "2024-01-17T13:58:25Z")

</div>

Hi!

What is the verison of your helm chart?

you can find it running:

> helm show chart weaviate/weaviate

Also, any reason for using 1.18.4 version and not a more recent one?

---

<div class="post-metadata">

**Author:** ![lina\_7amed](https://avatars.discourse-cdn.com/v4/letter/l/dc4da7/32.png) [@lina\_7amed](https://forum.weaviate.io/u/lina_7amed)\
**Post date:** [January 18, 2024, 3:11pm UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/5 "2024-01-18T15:11:14Z")

</div>

again i’m not using helm chart  
which version do you recommend to be compatible with scalability feature

---

<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:** [January 18, 2024, 3:40pm UTC](https://forum.weaviate.io/t/weaviate-scalability/1208/6 "2024-01-18T15:40:29Z")

</div>

Oh! Sorry, missed that part.

We strongely suggest using helm as it has everything necessary to deploy it in multi node scenario.

Or, you can use it as reference to do your own deployment.

There is this thread where you can use as base to deploy two nodes using docker-compose, and use the env vars for reference:

> [@Can only Docker Compose be used for multi node deployment?](https://forum.weaviate.io/t/can-only-docker-compose-be-used-for-multi-node-deployment/517/2):
>
> Hi @codehelen ! Welcome to our community slight_smile This must be some networking issue along the way, as your docker is correct (see below) A starting point is making sure that weaviate-node2-IP can communicate with weaviate-node1-IP on all specified ports. A good example on how to run with ad-hoc containers (at the same docker host): First, create a docker attachable network docker network create weaviate --atachable note that weaviate, above, can be whatever network name you want. Mak…