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

Error: ip limit during probes reconnect #404

Closed
alexey-yarmosh opened this issue Jul 25, 2023 · 2 comments · Fixed by #405 or #415
Closed

Error: ip limit during probes reconnect #404

alexey-yarmosh opened this issue Jul 25, 2023 · 2 comments · Fixed by #405 or #415
Assignees
Labels

Comments

@alexey-yarmosh
Copy link
Member

Usage of cached fetchSockets response in probe-ip-limit.ts leads to Error: ip limit.

Scenario:

  • probe1 is connected to the api
  • some operation (e.g. /probes ednpoint) calls fetchSockets
  • fetchSockets result (including probe1) is return and cached for 1 sec
  • during that 1 sec probe1 is reconnecting (e.g. because of ping timeout)
  • probe-ip-limit.ts calls fetchSockets and gets cached result (with probe1 in a list)
  • that lead to Error: ip limit
@jimaek
Copy link
Member

jimaek commented Aug 10, 2023

After deploy the issue seems to be still present. Logs provided

@alexey-yarmosh
Copy link
Member Author

ip limit issues is fixed. Sometimes timeout reached while waiting for fetchSockets response occurs, but it is not related to that issue. Closing this one and reopening #234 instead.

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