Update content/shared/v3-core-plugins/_index.md
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>pull/5940/head
parent
1c4baa9628
commit
fd3b48061b
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in New Issue