-
Notifications
You must be signed in to change notification settings - Fork 261
docs(srv): add ref on DNS query rate limit for faas caas MTA-5249 #3965
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| macro: dns-query-rate-limit | ||
| --- | ||
|
|
||
| ## DNS Query Rate Limiting | ||
|
|
||
| To ensure the stability and performance of our Serverless Functions and Containers platform, we have implemented a rate limit to the number of DNS queries that can be made by users. This rate limit is designed to prevent any single container instance from consuming excessive resources and impacting the performance of other users' functions and containers. | ||
|
|
||
| ## Rate Limit Details | ||
|
|
||
| The rate limit is set at **20 requests per second per function or container instance**. | ||
|
|
||
| This limit only applies to DNS queries that require a full resolution, such as queries for records that have not been previously resolved. | ||
| Queries for records that have already been resolved recently are not subject to this rate limit. | ||
|
|
||
| <Message type="important"> | ||
| The rate limit is applied per function or container instance, not per user or client. | ||
|
|
||
| The rate limit is therefore enforced independently for each function or container instance, regardless of the user or client that owns it. | ||
| </Message> | ||
|
|
||
| ## Effective Date | ||
|
|
||
| The DNS query rate limit will be enforced starting on November, 26th 2024. Any DNS queries made after this time will be subject to the rate limit. | ||
|
|
||
| ## Why Rate Limiting is Necessary | ||
|
|
||
| Our Serverless Functions and Containers platform is a shared infrastructure, which means that multiple users' functions or containers are running on the same nodes. In the past, we have experienced issues with high DNS query volumes from some function or container instances, which have impacted the performance of other users' containers. These issues have led to DNS resolution delays, timeouts, and other problems that affect the overall stability and performance of our platform. | ||
|
|
||
| To mitigate these issues, we have implemented rate limiting on DNS queries. By limiting the number of DNS queries that can be made by each function or container instance, we can prevent any single instance from consuming all available DNS resources and causing problems for other users. | ||
|
|
||
| <Message type="note"> | ||
| The 20 requests per second limit is far above the typical usage patterns we have seen from legitimate users, and it only applies to DNS queries that require a full resolution. Therefore, this rate limit should not impact most users. | ||
| </Message> | ||
|
|
||
| ## Impact on Legitimate Users | ||
|
|
||
| We understand that rate limiting may restrict some users' activities, but we believe that this is a necessary measure to ensure the overall stability and performance of our platform. Legitimate users who are making reasonable use of our platform should not be affected by this rate limit. In fact, rate limiting will help to ensure that our platform remains responsive and high-performing for all users, even in case of high traffic or malicious activity. | ||
|
|
||
| ## Optimizing DNS Query Usage | ||
|
|
||
| If you are experiencing issues with the DNS query rate limit, review your application's DNS query usage to see if there are any opportunities for optimization. | ||
|
|
||
| However, this rate limit is intended to prevent excessive DNS query volumes, and most users should not need to take any action to avoid hitting the limit. | ||
|
|
||
| ## Future Changes to the Rate Limit | ||
|
|
||
| Scaleway reserves the right to adjust the rate limit in the future as needed to ensure the stability and performance of our platform. We will notify users of any changes to the rate limit through our usual communication channels. | ||
|
|
||
| ## Additional Support | ||
|
|
||
| If you have specific needs that require a higher DNS query volume, you may be able to implement optimizations on the application side to reduce the number of DNS queries made. | ||
|
|
||
| [Contact the Scaleway Support](https://console.scaleway.com/support/tickets/create) for assistance if you encounter any issues or have questions about the DNS query rate limit. We're here to help you get the most out of our platform. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 changes: 17 additions & 0 deletions
17
serverless/containers/reference-content/dns-query-rate-limit.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| meta: | ||
| title: DNS query rate limiting | ||
| description: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. | ||
| content: | ||
| h1: DNS query rate limiting | ||
| paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Containers. | ||
| tags: serverless containers dns query rate limiting limit response | ||
| dates: | ||
| validation: 2024-11-12 | ||
| posted: 2024-11-12 | ||
| categories: | ||
| - serverless | ||
| - containers | ||
| --- | ||
|
|
||
| <Macro id="dns-query-rate-limit" /> |
17 changes: 17 additions & 0 deletions
17
serverless/functions/reference-content/dns-query-rate-limit.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| meta: | ||
| title: DNS query rate limiting | ||
| description: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. | ||
| content: | ||
| h1: DNS query rate limiting | ||
| paragraph: Information on how the DNS query rate limiting works with Scaleway Serverless Functions. | ||
| tags: serverless functions dns query rate limiting limit response | ||
| dates: | ||
| validation: 2024-11-12 | ||
| posted: 2024-11-12 | ||
| categories: | ||
| - serverless | ||
| - functions | ||
| --- | ||
|
|
||
| <Macro id="dns-query-rate-limit" /> |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.