Write Timeout for Batch Vectorization in Docker – TLS & Container Restart Issues

[Mohamed_Shahin]

Hey @Volvo

It’s great to have you in our community!

Have you tried to reduce the parallel processes to 1 or 2, or limit it to 100 objects at a time. It’s also worth checking that your network latency is good.

I’d also suggest ensuring the resources are sufficient in your cluster. Also, try increasing the connection timeout for Weaviate, especially for inserts:

additional_config=AdditionalConfig(
timeout=Timeout(init=30, query=240, insert=240),
)

Local instances | Weaviate

Regarding TLS configuration, please see the following example from my colleague @DudaNogueira regarding SSL/TLS

Does Weaviate support SSL out of the box?

hi @lakshminarayana ! Welcome to our community. Our documentation usually doesn’t cover the SSL/TLS side of the deployment for two main reasons: 1 - Usually, self deployments will not expose Weaviate directly. Their applications will be exposed. but not Weaviate. 2 - Whenever there is a reason to expose Weaviate under a SSL/TLS connection, one can use a variety of reverse proxies, load balancers and so on. I have crafted here a gist on how to deploy Weaviate, with a single node, using docker…

Regards,
Mohamed Shahin
Support Engineer