Chris Lu 43626431c3 vector: recheck master discovery quickly while no worker is cached (#12199) ...

The vectors gateway backs off discovery for 5s between resolutions, but
the backoff also suppressed rediscovery after an empty lookup. A worker
that landed its KeepConnected registration a moment after the first
query stayed invisible for the whole window — longer than a client's
retry budget — so the S3 Vectors e2e flaked: CreateIndex raced the
registration, got InternalFailure, and every boto retry fell inside the
same 5s fast-fail window.

With no cached backend, recheck every 500ms instead; the 5s interval now
only bounds membership refreshes against a live client, and an absent
worker still cannot flood the master with lookups. The empty-membership
error also becomes codes.Unavailable so the API answers 503 rather than
InternalFailure.

cluster.ps lists registered vector nodes like the other node types, and
the e2e harness polls it for the engine's registration instead of only
checking the gRPC port — a listening engine is not discoverable until
the registration lands.

2026-10-29 01:15:29 -07:00

..

Makefile

vector: weed-vector registers to master; s3 discovers it there (#12146)

2026-10-28 00:58:31 -07:00

run_test.sh

vector: recheck master discovery quickly while no worker is cached (#12199)

2026-10-29 01:15:29 -07:00

s3.json

test/vectors: fix the S3 Vectors e2e harness (#12112)

2026-10-26 17:52:05 -07:00

s3vectors_test.py

vector: weed-vector registers to master; s3 discovers it there (#12146)

2026-10-28 00:58:31 -07:00