Async batch insert requires extended timeout configuration
infoperformanceUpdated Mar 31, 2025
Technologies:
How to detect:
When performing async batch inserts with WeaviateAsyncClient and large document sets, insufficient timeout values can cause operations to fail or appear stalled. The insert operation specifically requires longer timeout than query operations.
Recommended action:
Configure AdditionalConfig with Timeout object specifying separate timeouts for different operations: init=30, query=60, insert=120 (all values in seconds). The 120-second insert timeout accommodates bulk batch operations. Set skip_init_checks=False to ensure connection is validated.