Imported Google Group message.
Date:Tuesday, 17 March 2015 12:01:53 UTC.
This is a bug, there's currently no re-connect handling capability for Mongo, only for redis, it's definetely something we'll need to add in.
The thing is, in the gateway, there are two separate components that talk to Mongo, the analytics purger (the error you're describing above) and the API Definition loader (this only runs on reload), I'm not sure if the db connection redials on a reload, so that needs investigating. either way, it should be possible to force a connect in these instances.
With the Gateway it's a different story, the storage interface has a connect function, but connection checks will need to be added across all of the different models, which might be a larger task!
Can you raise a GH issue please?
- show quoted text -