Handle cases when mongo is unavailable

[digitalshawn]

Processing and data insertion scripts exit with an exception when mongo is unavailable

[jhemsley]

A bit lame of me not to handle this case. There are a zillion ways I could implement a fix for this.
Here are the cases as I see it:

1. happens right at system startup
2. happens during run

Here is one scenario. I'm interested in your thoughts:
Assume issue 7 (log connection error) is fixed.

If Mongo isn't available, log an error once, go into an increasing wait time loop and try again, logging a warning for each fail.

Increasing wait time: starting at one second, double wait time 12 times. Log another error. Gives us a 35 minute wait. Keep trying at that wait time for 100 times(?).

This seems reasonable to me for the cases above for all three processes.