Closed jobrieniii closed 9 years ago
Could not fully reproduce this issue on local machine.
Not sure if this possibly resulted when mongo container was still being started (which was when the issue was noted during a deployment to dev).
To be proactive and warm a newly created / refreshed mongodb, a db.createCollection is called for each collection defined in the config during app server startup.
APIs result in 500 errors and bad error message.
Recommend that we confirm the collections are in place at startup in node.