Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Commit

Permalink
fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
wojcik-dorota committed Nov 27, 2023
1 parent 6ca3992 commit 08519bc
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 3 deletions.
1 change: 1 addition & 0 deletions .github/vale/dicts/aiven.dic
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ ARN
Astacus
Auth0
autojoin
autoscaler
autovacuum
Avro
AZ
Expand Down
1 change: 1 addition & 0 deletions .github/vale/styles/Aiven/capitalization_headings.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ exceptions:
- Business
- BYOC
- Cassandra
- CLI
- ClickHouse
- CloudWatch
- Cloud Logging
Expand Down
6 changes: 3 additions & 3 deletions docs/platform/howto/disk-autoscaler.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,16 @@ Service disk autoscaler increases disk storage capacity automatically when the d
How it works
------------

There are a few steps illustratig how disk autoscaler works:
There are a few steps illustrating how disk autoscaler works:

1. You create an disk autoscaler integration endpoint in your Aiven project setting the maximum additional storage at the same time.
2. You enable a disk autoscaler integration for your service using the new disk autoscaler integration endpoint.
3. From that point onward, the evaluation of disk space availability for your service is done every 30 seconds.
4. When disk storage consumption reaches the treshold for a specific service, disk autoscaler increases available storage space by 10% every time taking the currently-used service plan as a baseline.
4. When disk storage consumption reaches the threshold for a specific service, disk autoscaler increases available storage space by 10% every time taking the currently-used service plan as a baseline.

.. topic:: AUTOSCALE THRESHOLDS PER SERVICE TYPE

The treshold at which disk autoscaling is triggered is a percentage of the available disk storage capacity and depends on a service type:
The threshold at which disk autoscaling is triggered is a percentage of the available disk storage capacity and depends on a service type:

Check failure on line 27 in docs/platform/howto/disk-autoscaler.rst

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/platform/howto/disk-autoscaler.rst#L27

[Aiven.aiven_spelling] 'autoscaling' does not seem to be a recognised word
Raw output
{"message": "[Aiven.aiven_spelling] 'autoscaling' does not seem to be a recognised word", "location": {"path": "docs/platform/howto/disk-autoscaler.rst", "range": {"start": {"line": 27, "column": 32}}}, "severity": "ERROR"}

* Aiven for Apache Cassandra®: 35% of the available disk storage capacity
* Aiven for OpenSearch®: 75% of the available disk storage capacity
Expand Down

0 comments on commit 08519bc

Please sign in to comment.