From fd3b48061b974043e966c84a67365a02addeafec Mon Sep 17 00:00:00 2001 From: Jameelah Mercer <36314199+MeelahMe@users.noreply.github.com> Date: Thu, 3 Apr 2025 16:45:55 -0700 Subject: [PATCH] Update content/shared/v3-core-plugins/_index.md Co-authored-by: Jason Stirnaman --- content/shared/v3-core-plugins/_index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/shared/v3-core-plugins/_index.md b/content/shared/v3-core-plugins/_index.md index cdd2a49ba..4a980e6b1 100644 --- a/content/shared/v3-core-plugins/_index.md +++ b/content/shared/v3-core-plugins/_index.md @@ -38,16 +38,18 @@ influxdb3 serve \ Replace `/path/to/plugins` with the directory where you want to store your Python plugin files. All plugin files must be located in this directory or its subdirectories. -{{% show-in "enterprise" %}} + ### Configure distributed environments If you're running multiple InfluxDB instances (distributed deployment): 1. Decide where plugins should run +{{% show-in "enterprise" %}} - Data processing plugins, such as WAL plugins, run on ingestor nodes - HTTP-triggered plugins run on nodes handling API requests - Scheduled plugins can run on any configured node +{{% /show-in %}} 2. Enable plugins on selected instances 3. Maintain identical plugin files across all instances where plugins run - Use shared storage or file synchronization tools to keep plugins consistent @@ -57,7 +59,6 @@ If you're running multiple InfluxDB instances (distributed deployment): > > Configure your plugin directory on the same system as the nodes that run the triggers and plugins. -{{% /show-in %}} ## Add a Processing engine plugin