You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
search: skipped spaces KV only works with events enabled #3968
search server opens the search-skipped-spaces KV only if SEARCH_EVENTS_DISABLED is false. The same flag starts the event consumer.
A search server that only serves IndexSpace which is triggered by the cli grpc client when the reindex command is manually executed. If no KV is available, disabled spaces are not "remembered" in NATS, these spaces are then never reindexed after the SpaceEnabled event.
We need this for a standalone reindex job in the helm chart, which must not consume search events.
Proposal: open the KV whenever a NATS endpoint is configured, independent of SEARCH_EVENTS_DISABLED.
ah so the events connection is reused for the store. I would consider this a bug. we may need to introduce a proper store as in the other services that do both: consume events and use a kv store.
that would be the correct fix. a better design for later might be to actually reuse the connection and use the *_CACHE_STORE=noop env var to disable the cache and *_EVENTS_DISABLED=true to disable the consumer/subscriber... 🤔 hm but maybe you want to use different nats clusters for events and caches ... so for now: introduce SEARCH_CACHE_STORE* vars and use a dedicated connection for the kv store
Activity
butonic commentedon Nov 12, 2026
ah so the events connection is reused for the store. I would consider this a bug. we may need to introduce a proper store as in the other services that do both: consume events and use a kv store.
that would be the correct fix. a better design for later might be to actually reuse the connection and use the
*_CACHE_STORE=noopenv var to disable the cache and*_EVENTS_DISABLED=trueto disable the consumer/subscriber... 🤔 hm but maybe you want to use different nats clusters for events and caches ... so for now: introduceSEARCH_CACHE_STORE*vars and use a dedicated connection for the kv store