POC changes for making search plugin hot reloadable #19882
+1,246
−9
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 is a Proof of Concept demonstrating dynamic loading of search plugins with custom query types at runtime without cluster restart. Currently supports queries only and requires security hardening before production use.
Related PR: #19809
What This POC Includes
What This POC Does NOT Include
Critical Missing Features:
Problem
OpenSearch currently requires full cluster restarts to add or update search plugins, causing operational overhead and deployment complexity.
Solution
Dynamic plugin lifecycle with immediate query availability:
Key Changes
New Components:
SearchPluginHotReloadService- Orchestrates plugin loading and registry updatesLoadSearchPluginsActionwith REST endpoint:POST /_search_plugins/loadModified Components:
SearchModule- Added dynamic query tracking (ConcurrentHashMap)IndicesService,IndexService,AbstractHttpServerTransport- Changed registry references from final to volatile, added update methodsPluginsService- AddedloadPluginDynamically()methodActionModule,Node- Wired new service into dependency graphSecurity.java,security.policy- Temporarily disabled/relaxed for POCArchitecture
Registry propagation chain:
Thread safety via volatile references and atomic registry swaps.
API Usage
Testing
Breaking Changes
None. Additive and backward compatible.