edits w Larissa
parent
35ae59244a
commit
07e2158774
|
@ -5,7 +5,7 @@ Description: >
|
|||
menu:
|
||||
enterprise_influxdb_1_8:
|
||||
weight: 40
|
||||
parent: Guides
|
||||
parent: Guides
|
||||
---
|
||||
|
||||
Review configuration and hardware guidelines for InfluxDB Enterprise:
|
||||
|
@ -17,13 +17,13 @@ Review configuration and hardware guidelines for InfluxDB Enterprise:
|
|||
* [Recommended cluster configurations](#recommended-cluster-configurations)
|
||||
* [Storage: type, amount, and configuration](#storage-type-amount-and-configuration)
|
||||
|
||||
For OSS hardware sizing guidelines, click on following [LINK](https://docs.influxdata.com/influxdb/v1.8/guides/hardware_sizing/).
|
||||
For InfluxDB OSS instances, see [OSS hardware sizing guidelines](https://docs.influxdata.com/influxdb/v1.8/guides/hardware_sizing/).
|
||||
|
||||
> **Disclaimer:** Your numbers may vary from recommended guidelines. Guidelines provide estimated benchmarks for implementing the most performant system for your business.
|
||||
|
||||
## Enterprise overview
|
||||
|
||||
InfluxDB Enterpise supports the following:
|
||||
InfluxDB Enterprise supports the following:
|
||||
|
||||
- more than 750,000 field writes per second
|
||||
- more than 100 moderate queries per second ([see Query guides](#query-guidelines))
|
||||
|
|
|
@ -24,7 +24,7 @@ For InfluxDB OSS instances, see [OSS hardware sizing guidelines](https://docs.in
|
|||
|
||||
## Enterprise overview
|
||||
|
||||
InfluxDB Enterpise supports the following:
|
||||
InfluxDB Enterprise supports the following:
|
||||
|
||||
- more than 750,000 field writes per second
|
||||
- more than 100 moderate queries per second ([see Query guides](#query-guidelines))
|
||||
|
@ -45,7 +45,7 @@ If you want a single node instance of InfluxDB that's fully open source, require
|
|||
For **simple** or **complex** queries, we recommend testing and adjusting the suggested requirements as needed. Query complexity is defined by the following criteria:
|
||||
|
||||
| Query complexity | Criteria |
|
||||
|------------------|---------------------------------------------------------------------------------------|
|
||||
|:------------------|:---------------------------------------------------------------------------------------|
|
||||
| Simple | Have few or no functions and no regular expressions |
|
||||
| | Are bounded in time to a few minutes, hours, or 24 hours at most |
|
||||
| | Typically execute in a few milliseconds to a few dozen milliseconds |
|
||||
|
@ -60,7 +60,7 @@ For **simple** or **complex** queries, we recommend testing and adjusting the su
|
|||
|
||||
### Meta nodes
|
||||
|
||||
> Set up clusters with an odd number of meta nodes──an even number may cause issues in certain configurations.
|
||||
> Set up clusters with an odd number of meta nodes─an even number may cause issues in certain configurations.
|
||||
|
||||
A cluster must have a **minimum of three** independent meta nodes for data redundancy and availability. A cluster with `2n + 1` meta nodes can tolerate the loss of `n` meta nodes.
|
||||
|
||||
|
|
|
@ -74,7 +74,7 @@ Estimated guidelines include writes per second, queries per second, and number o
|
|||
|
||||
### Meta nodes
|
||||
|
||||
> Set up clusters with an odd number of meta nodes──an even number may cause issues in certain configurations.
|
||||
> Set up clusters with an odd number of meta nodes─an even number may cause issues in certain configurations.
|
||||
|
||||
A cluster must have a **minimum of three** independent meta nodes for data redundancy and availability. A cluster with `2n + 1` meta nodes can tolerate the loss of `n` meta nodes.
|
||||
|
||||
|
|
|
@ -39,7 +39,7 @@ If you want a single node instance of InfluxDB that's fully open source, require
|
|||
For **simple** or **complex** queries, we recommend testing and adjusting the suggested requirements as needed. Query complexity is defined by the following criteria:
|
||||
|
||||
| Query complexity | Criteria |
|
||||
|------------------|---------------------------------------------------------------------------------------|
|
||||
|:------------------|:---------------------------------------------------------------------------------------|
|
||||
| Simple | Have few or no functions and no regular expressions |
|
||||
| | Are bounded in time to a few minutes, hours, or 24 hours at most |
|
||||
| | Typically execute in a few milliseconds to a few dozen milliseconds |
|
||||
|
|
|
@ -44,7 +44,7 @@ For more information about sizing requirements for InfluxDB Enterprise, see [Inf
|
|||
For **simple** or **complex** queries, we recommend testing and adjusting the suggested requirements as needed. Query complexity is defined by the following criteria:
|
||||
|
||||
| Query complexity | Criteria |
|
||||
|:------------------|---------------------------------------------------------------------------------------|
|
||||
|:-----------------|:---------------------------------------------------------------------------------------|
|
||||
| Simple | Have few or no functions and no regular expressions |
|
||||
| | Are bounded in time to a few minutes, hours, or 24 hours at most |
|
||||
| | Typically execute in a few milliseconds to a few dozen milliseconds |
|
||||
|
|
Loading…
Reference in New Issue