Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

InfluxDB 3 Note fixes (#5837)

pull/5844/head
meelahme 2025-02-18 17:21:01 -08:00
parent 76718055be
commit f213e9692d
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/shared/v3-enterprise-get-started/_index.md
View File

@ -963,19 +963,18 @@ Congratulations, you have a robust setup to workload isolation using {{% product
### Writing and Querying for Multi-Node Setups
If you’re running {{% product-name %}} in a single-instance setup, writing and querying is the same as for {{% product-name %}}.
You can use the default port `8181` for any write or query, without changing any of the commands.
> [!Note]
> #### Specify hosts for writes and queries
>
> To benefit from this multi-node, isolated architecture specify hosts:
> To benefit from this multi-node, isolated architecture, specify hosts:
>
> - In write requests, specify a host designated for _write-only_
> - In query requests, specify a host designated for _read-only
> - In write requests, specify a host designated for _write-only_.
> - In query requests, specify a host designated for _read-only_.
>
> When running multiple local instances for testing, or separate nodes in production, specifying the host ensures writes and queries are routed to the correct instance.
> If you run locally and serve an instance on 8181 (the default port), then you don’t need to specify the host.
> When running multiple local instances for testing or separate nodes in production, specifying the host ensures writes and queries are routed to the correct instance.
> If you run locally and serve an instance on 8181 (the default port), you don’t need to specify the host.
```
# Example variables on a query