I'm working on a library that opens a number of different RethinkDB client connections and I've been getting the following error sporadically (i.e. if I run tests 20 times this'll show up in maybe 5% of them, which suggests some sort of race condition somewhere).
The thing is that I usually expect an error like this to surface on the server side rather than on the client-side - in other words, the error seems to me to suggest that the driver is attempting to claim a socket that is currently held by the RethinkDB server. I'll concede, however, that I don't actually know what I'm talking about here, so my inference could be completely off.
Is this something that might just happen when the client attempts to open more than one connection to the server at once and the latter attempt fails? What's a good way of handling this?
This seems to have been an issue with the RethinkDB server repeatedly trying to give out the same connection port - re-starting the database has caused this error to stop showing up. Sorry for the false alarm.
Hey there!
I'm working on a library that opens a number of different RethinkDB client connections and I've been getting the following error sporadically (i.e. if I run tests 20 times this'll show up in maybe 5% of them, which suggests some sort of race condition somewhere).
The thing is that I usually expect an error like this to surface on the server side rather than on the client-side - in other words, the error seems to me to suggest that the driver is attempting to claim a socket that is currently held by the RethinkDB server. I'll concede, however, that I don't actually know what I'm talking about here, so my inference could be completely off.
Is this something that might just happen when the client attempts to open more than one connection to the server at once and the latter attempt fails? What's a good way of handling this?