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

Update hardware_sizing.md 

removed web node from enterprise 1.8 hardware sizing guideline
pull/3389/head
lwandzura 2021-11-10 14:12:45 -06:00 committed by GitHub
parent 60d5c84167
commit 0781e8ce43
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/enterprise_influxdb/v1.8/guides/hardware_sizing.md
View File

@ -69,16 +69,6 @@ Meta nodes do not need very much computing power. Regardless of the cluster load
* RAM: 512 MB - 1 GB
* IOPS: 50
### Web node
The InfluxDB Enterprise web server is primarily an HTTP server with similar load requirements. For most applications, the server doesn't need to be very robust. A cluster can function with only one web server, but for redundancy, we recommend connecting multiple web servers to a single back-end Postgres database.
> **Note:** Production clusters should not use the SQLite database (lacks support for redundant web servers and handling high loads).
* vCPU or CPU: 2-4 cores
* RAM: 2-4 GB
* IOPS: 100
### Data nodes
A cluster with one data node is valid but has no data redundancy. Redundancy is set by the [replication factor](/influxdb/v1.8/concepts/glossary/#replication-factor) on the retention policy the data is written to. Where `n` is the replication factor, a cluster can lose `n - 1` data nodes and return complete query results.