From 0781e8ce4321fd8f5090d389be28c34159693f01 Mon Sep 17 00:00:00 2001
From: lwandzura <51929958+lwandzura@users.noreply.github.com>
Date: Wed, 10 Nov 2021 14:12:45 -0600
Subject: [PATCH] Update hardware_sizing.md

removed web node from enterprise 1.8 hardware sizing guideline
---
 .../enterprise_influxdb/v1.8/guides/hardware_sizing.md | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/content/enterprise_influxdb/v1.8/guides/hardware_sizing.md b/content/enterprise_influxdb/v1.8/guides/hardware_sizing.md
index 04021e02a..f089971cc 100644
--- a/content/enterprise_influxdb/v1.8/guides/hardware_sizing.md
+++ b/content/enterprise_influxdb/v1.8/guides/hardware_sizing.md
@@ -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.