Changed timeout on mongo wait after restore

Changed timeout on mongo wait after restore

Bug 1291022 was caused by a race condition.
After restore, there was a period of wait until
mongodb would come up. The timeout value was set 
too low for cases where connectio to the server
was too fast. On slow connections there was extra
time produced by the wait for the server answer
to the polling. I changed the timeout value and 
tested in a machine in the same region than
the environment created, it stopped failing after
the change.

https://code.launchpad.net/~hduran-8/juju-core/1291022_remove_race_condition_waiting_machine/+merge/214118

(do not edit description out of merge proposal)

[hduran, 2014-04-03 20:55:07]

Please take a look.

[natefinch, 2014-04-03 20:56:52]

LGTM

[rog, 2014-04-04 11:30:51]

LGTM modulo the below.

https://codereview.appspot.com/82280045/diff/1/cmd/plugins/juju-restore/resto...
File cmd/plugins/juju-restore/restore.go (right):

https://codereview.appspot.com/82280045/diff/1/cmd/plugins/juju-restore/resto...
cmd/plugins/juju-restore/restore.go:128: #Used to be 2, that is not enough when
we are too close in terms of network
As suggested online, I suggest 100 iterations of 5 seconds.
I don't think the comment adds much value FWIW.

[hduran, 2014-04-04 11:35:16]

Please take a look.

https://codereview.appspot.com/82280045/diff/1/cmd/plugins/juju-restore/resto...
File cmd/plugins/juju-restore/restore.go (right):

https://codereview.appspot.com/82280045/diff/1/cmd/plugins/juju-restore/resto...
cmd/plugins/juju-restore/restore.go:128: #Used to be 2, that is not enough when
we are too close in terms of network
On 2014/04/04 11:30:51, rog wrote:
> As suggested online, I suggest 100 iterations of 5 seconds.
> I don't think the comment adds much value FWIW.

Done.