# Cannot Add Node to Cluster on AWS ECS **URL:** \ **Category:** Support\ **Created:** [June 26, 2024, 9:42pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816 "2024-06-26T21:42:27Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![dhanshew72](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dhanshew72/32/1809_2.png) [@dhanshew72](https://forum.weaviate.io/u/dhanshew72)\ **Post date:** [June 26, 2024, 9:42pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/1 "2024-06-26T21:42:27Z")
### Description I’m attempting to add an extra node onto an ECS cluster using Weaviate and I keep getting the following error message: ```auto received invalid msgType (72), expected pushPullMsg (6) memberlist join not successful ``` I’m trying to connect via a load balancer if that changes anything. Any ideas on what might be causing this? ### Server Setup Information - Weaviate Server Version: 1.24.13 - Deployment Method:Docker on ECS - Multi Node? Number of Running Nodes: Attempting to do 2 - Client Language and Version: 4.6.1 - Multitenancy?: Yes ### Any additional Information I’m using AWS ECS, so I don’t have the luxury of doing service to service connection like in Kubernetes. Should I be using something like service discovery for this? Any ideas/thoughts would be appreciated. ---
**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:** [June 27, 2024, 9:27pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/2 "2024-06-27T21:27:14Z")
hi @dhanshew72 !! Can you get more logs on this for context? Also, you should know that from 1.24 to 1.25 we have some important changes for multi node setups. > **[1.25 (For Kubernetes users) | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/more-resources/migration/weaviate-1-25)** > > Assumptions & requirements Considering that if not a multi tenant use case, adding a new node to your cluster will not be enough: you would need to reindex your collection to a new one with the desired replica factor. As you have a multi tenant, adding a new node will get new tenants with the node is ready. Can you replicate this on a non ECS deployment? Thanks! ---
**Author:** ![dhanshew72](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dhanshew72/32/1809_2.png) [@dhanshew72](https://forum.weaviate.io/u/dhanshew72)\ **Post date:** [June 28, 2024, 5:12pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/3 "2024-06-28T17:12:27Z")
Do you have a doc on multi-tenant with multi-node setups? How many would I need to support this? FYI: I’m doing a POC so I’m not locked into migrating data quite yet. ---
**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:** [June 28, 2024, 7:25pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/4 "2024-06-28T19:25:31Z")
Hi! For multi node, the preferred way is deploying thru our helm chart in k8s: > **[GitHub - weaviate/weaviate-helm: Helm charts to deploy Weaviate to k8s](https://github.com/weaviate/weaviate-helm)** > > Helm charts to deploy Weaviate to k8s. Contribute to weaviate/weaviate-helm development by creating an account on GitHub. Now, both single and multi node can handle multi tenants. Here is the doc for multi tenant operation: > **[Multi-tenancy operations | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/manage-data/multi-tenancy)** > > Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant. If your application serves many different users, multi-tenancy keeps their data private and makes database... And here a recipe on how to play around with MT: > **[recipes/weaviate-features/multi-tenancy at main · weaviate/recipes](https://github.com/weaviate/recipes/tree/main/weaviate-features/multi-tenancy)** > > This repository shares end-to-end notebooks on how to use various Weaviate features and integrations! - weaviate/recipes Let me know if this helps. Thanks! ---
**Author:** ![dhanshew72](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dhanshew72/32/1809_2.png) [@dhanshew72](https://forum.weaviate.io/u/dhanshew72)\ **Post date:** [July 1, 2024, 11:18pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/5 "2024-07-01T23:18:28Z")
This helped, I’m using Langchain so I dug in to figure out how to apply in on that end. My main question, can you shard an individual tenant? ---
**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:** [July 1, 2024, 11:20pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/6 "2024-07-01T23:20:56Z")
Hi! It is already sharded. All tenants have it’s own shard. [from the docs](https://weaviate.io/developers/weaviate/manage-data/multi-tenancy): > Multi-tenancy provides data isolation. Each tenant is stored on a separate shard. Data stored in one tenant is not visible to another tenant. If your application serves many different users, multi-tenancy keeps their data private and makes database operations more efficient. 😉 ---
**Author:** ![dhanshew72](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dhanshew72/32/1809_2.png) [@dhanshew72](https://forum.weaviate.io/u/dhanshew72)\ **Post date:** [July 1, 2024, 11:59pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/7 "2024-07-01T23:59:59Z")
My apologies, to clarify: Can I split a tenant into 2 shards for a possible setup? Or is it better to use something like replication? ---
**Author:** ![dhanshew72](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dhanshew72/32/1809_2.png) [@dhanshew72](https://forum.weaviate.io/u/dhanshew72)\ **Post date:** [July 2, 2024, 6:54pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/8 "2024-07-02T18:54:11Z")
Found a solution to this. Using service discovery, you still have to open the ports and attach a security group to get this error to go away. Basically, any port you have configured in environment CLUSTER\_GOSSIP\_BIND\_PORT, CLUSTER\_DATA\_BIND\_PORT needs to be opened in the security group. ---
**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:** [July 3, 2024, 6:45pm UTC](https://forum.weaviate.io/t/cannot-add-node-to-cluster-on-aws-ecs/2816/9 "2024-07-03T18:45:21Z")
Nice! Thanks for sharing.