This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Respond with backoff message under load #658
Comments
bbangert
added a commit
that referenced
this issue
Oct 5, 2016
Several db operations from websocket clients now handle provisioned exceeded errors more gracefully. Register now returns an error message about the overload so that a client may retry. During the initial notification check, if an error occurs the notification check is re-scheduled to occur at a later time. Finally, if the provision error hits during the monthly change-over, the client remains connected and the migration is re-scheduled. Closes #658
bbangert
added a commit
that referenced
this issue
Oct 5, 2016
Several db operations from websocket clients now handle provisioned exceeded errors more gracefully. Register now returns an error message about the overload so that a client may retry. During the initial notification check, if an error occurs the notification check is re-scheduled to occur at a later time. Finally, if the provision error hits during the monthly change-over, the client remains connected and the migration is re-scheduled. Closes #658
bbangert
added a commit
that referenced
this issue
Oct 6, 2016
Several db operations from websocket clients now handle provisioned exceeded errors more gracefully. Register now returns an error message about the overload so that a client may retry. During the initial notification check, if an error occurs the notification check is re-scheduled to occur at a later time. Finally, if the provision error hits during the monthly change-over, the client remains connected and the migration is re-scheduled. Closes #658
bbangert
added a commit
that referenced
this issue
Oct 6, 2016
Several db operations from websocket clients now handle provisioned exceeded errors more gracefully. Register now returns an error message about the overload so that a client may retry. During the initial notification check, if an error occurs the notification check is re-scheduled to occur at a later time. Finally, if the provision error hits during the monthly change-over, the client remains connected and the migration is re-scheduled. Closes #658
bbangert
added a commit
that referenced
this issue
Oct 6, 2016
Several db operations from websocket clients now handle provisioned exceeded errors more gracefully. Register now returns an error message about the overload so that a client may retry. During the initial notification check, if an error occurs the notification check is re-scheduled to occur at a later time. Finally, if the provision error hits during the monthly change-over, the client remains connected and the migration is re-scheduled. Closes #658
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the connection nodes hit provisioned exceptions for client commands, instead of dropping the client they should respond with an error message indicating the client should retry soon.
The text was updated successfully, but these errors were encountered: