feat(llm): add periodic availability checking for LLM clients #3022
+466
−16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds periodic availability checking for all LLM clients (OpenAI, Gemini, Ollama) to improve performance and provide proactive status monitoring. The availability state is now cached and updated in the background, eliminating blocking API calls on each availability check request.
Changes Made
Core Implementation
TimeoutManagercachedAvailabilityfield with volatile semantics for thread-safe reads without synchronization overheadrag.llm.typematches the client name, reducing unnecessary resource usageLLM Client Updates
Configuration
rag.llm.availability.check.intervalproperty (default: 60 seconds)gpt-5-minigemini-2.5-flashResource Management
destroy()method to all LLM clients for proper cleanuppreDestroyconfiguration infess_llm.xmlfor lifecycle managementTesting
Breaking Changes
None. The availability checking is backward-compatible:
Additional Notes
rag.chat.enabled=true)