Skip to content

Commit 0dfc37b

Browse files
claudespicelukekim
authored andcommitted
fix: Clarify that Elasticsearch data connector does not retry read operations
The deployment guide stated the data connector retries transient errors, but the retry mechanism (with_retry) is only wired into bulk_index on the vector engine write path. The data connector's get_mapping and search calls do not use retries — failures are surfaced immediately. Verified against spiceai/spiceai trunk at crates/elasticsearch/src/lib.rs (with_retry scoped to bulk_index, lines 247-253).
1 parent ac494f9 commit 0dfc37b

1 file changed

Lines changed: 2 additions & 7 deletions

File tree

  • website/docs/components/data-connectors/elasticsearch

website/docs/components/data-connectors/elasticsearch/deployment.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,9 @@ The connector does not currently expose certificate-pinning or custom CA-bundle
4141

4242
### Retries
4343

44-
The underlying HTTP client retries transient Elasticsearch errors (HTTP 429 and 5xx) and connection-level failures with exponential backoff. The data connector uses the client's defaults:
44+
The Elasticsearch client library includes a retry mechanism with exponential backoff for transient errors (HTTP 429 and 5xx). However, retries are currently only active on the **write path** used by the [Elasticsearch Vector Engine](../../vectors/elasticsearch) (`bulk_index` operations). The data connector's read operations (`_search`, `_mapping`) do **not** retry transient errors — failures are surfaced immediately.
4545

46-
| Setting | Default | Notes |
47-
| ----------------- | ------- | --------------------------------------------------------------------------- |
48-
| Max retries | `3` | Each subsequent attempt doubles the backoff, capped at `30s`. |
49-
| Initial backoff | `200ms` | Doubled per retry up to `30s`. |
50-
51-
Retry tuning is exposed only on the [Elasticsearch Vector Engine](../../vectors/elasticsearch) (`elasticsearch_max_retries`, `elasticsearch_retry_initial_backoff`); the data connector currently uses the defaults.
46+
Retry tuning is exposed only on the [Elasticsearch Vector Engine](../../vectors/elasticsearch) (`elasticsearch_max_retries`, `elasticsearch_retry_initial_backoff`).
5247

5348
### Timeouts
5449

0 commit comments

Comments
 (0)