You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we are not making any queries for a long time, we can meet a RethinkDBError with type CONNECTION. Why the library is not handling such a case by itselves? As well there is no option to set minimum of existing connections at a time, so we have to write a wrapper above .run() which checks if connection error is thrown or not.
Exact message of error is "The connection was closed before the query could be completed".
Node v12.13.1
Package version 2.4.0-rc.16
Any other needed information can be provided
The text was updated successfully, but these errors were encountered:
never encountered that kind of error before but I'm guessing if you set a ping interval you can avoid it, ping interval is in milliseconds and it sends a ping to all open connections for every interval amount of time
If we are not making any queries for a long time, we can meet a
RethinkDBError
with typeCONNECTION
. Why the library is not handling such a case by itselves? As well there is no option to set minimum of existing connections at a time, so we have to write a wrapper above.run()
which checks if connection error is thrown or not.Exact message of error is "The connection was closed before the query could be completed".
Node v12.13.1
Package version 2.4.0-rc.16
Any other needed information can be provided
The text was updated successfully, but these errors were encountered: