Skip to content
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

Throttling reset requests #187

Closed
jirenius opened this issue Mar 17, 2021 · 1 comment
Closed

Throttling reset requests #187

jirenius opened this issue Mar 17, 2021 · 1 comment

Comments

@jirenius
Copy link
Collaborator

Issue

When Resgate receives a system.reset request, it will generate get and/or access requests for all matching resources.
If a lot of resources matches the pattern, the service(s) may be overwhelmed, failing to respond within Resgate's default timeout period of 3 seconds. This will in turn result in Resgate sending unsubscribe events to the clients for any timed out resource.

Solution

It should be possible to throttle the number of concurrent requests being sent on system.reset. This can be done by introducing a single integer configuration value:

  • resetThrottle - integer value telling how many concurrent requests to have running at the same time for any single system.reset event.
jirenius added a commit that referenced this issue May 26, 2021
jirenius added a commit that referenced this issue Aug 25, 2021
…t-requests

Feature/gh 187 throttling reset requests
@jirenius
Copy link
Collaborator Author

Resolved in PR #201

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant