Hello! I’m currently working with Weaviate 1.26.14 (I’ve updated from 1.25.27) and have a bunch of problems: Information We have a 3-node cluster with 46mln objects each. Each node has been deployed with k8s and has 30 request cpu and 40 limit and both 500GiB request and limit for RAM Environment…

Hello @d_khlebokazov , if your objetive is to use async replication then upgrading to 1.29 should be highly recommended. I’d only suggest to use async replication in 1.26 in case of need and impediment of upgrading. With regards to performance, in 1.29 it was possible to repair 1mi objects in less …

[QUESTION] Async replication hashbeat fails with context deadline timeout

Support

d_khlebokazov February 25, 2025, 5:12am 4

It seems to be similar to Async_replication context deadline exceeded, unable to Activate Tenant

Was it possible to find a solution? @jeronimo_irazabal

Topic		Replies	Views
Async_replication context deadline exceeded, unable to Activate Tenant Support bug , python , technical	3	133	December 19, 2024
Write timeout in combination with replicas Support wcs , technical	18	246	April 22, 2025
Weaviate cluster is very unstable (1.29.2) Support	8	146	April 9, 2025
Context Deadline Exceeded Support technical	11	69	May 3, 2025
Batch inserts failing for weaviate Support python , technical	8	143	September 17, 2024

[QUESTION] Async replication hashbeat fails with context deadline timeout

Related topics