-
Notifications
You must be signed in to change notification settings - Fork 240
Adding info on index limits per project #5184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
af5ddd2
35f28c2
cd77034
f689b61
8416178
da6d765
bfa526d
dd18876
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -43,7 +43,7 @@ Afterwards, you can: | |
|
|
||
| **Management free:** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, and business continuity. | ||
|
|
||
| **Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. | ||
| **Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. Some [project-level limits](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits) apply to ensure performance and stability. Certain limits are adjustable by request. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @yetanothertw , at the moment, in event of a customer exceeding this limit, they will receive a 400 bad request error for their REST calls. The exception will contain a link to this
This link is coded in https://github.com/elastic/elasticsearch/blob/main/server/src/main/resources/org/elasticsearch/common/reference-docs-links.txt#L41. I will follow up with code change to point to this new URL.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Many thanks!
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @zhubotang-wq, should we wait until the code change is complete before we merge the docs? Or is it okay to merge now?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @yetanothertw let's please wait - we're still finalizing a decision on the actual number of indices to apply as the limit.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No worries, @pete-naylor. Please let me know when you're ready 👍 |
||
|
|
||
| **Optimized data storage:** Your data is stored in cost-efficient, general storage. A cache layer is available on top of the general storage for recent and frequently queried data that provides faster search speed. The size of the cache layer and the volume of data it holds depend on [settings](../../../deploy-manage/deploy/elastic-cloud/project-settings.md) that you can configure for each project. | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.