Increase mongo timeout at bootstrap

Increase mongo timeout at bootstrap

A small tweak to allow the bootstrap command
5 minutes to connnect to mongo before timing out.
This is needed because some machines are slow
and mongo does not start fast enough.

https://code.launchpad.net/~wallyworld/juju-core/increase-mongo-bootstrap-timeout/+merge/220745

(do not edit description out of merge proposal)

[wallyworld, 2014-05-23 05:15:13]

Please take a look.

[axw, 2014-05-23 06:34:08]

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go
File cmd/jujud/bootstrap.go (right):

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go#newcode145
cmd/jujud/bootstrap.go:145: state.DefaultDialOpts(),
I think we also want a longer timeout here, or maybe just a retry loop.

[wallyworld, 2014-05-23 07:07:58]

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go
File cmd/jujud/bootstrap.go (right):

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go#newcode145
cmd/jujud/bootstrap.go:145: state.DefaultDialOpts(),
On 2014/05/23 06:34:07, axw wrote:
> I think we also want a longer timeout here, or maybe just a retry loop.

Not sure. By the time agent.InitializeState() is called, startMongo() with the
longer timeout has already been called and a connection to mongo established. So
here I think it's ok to stick to the default timeout?

[axw, 2014-05-23 07:21:50]

LGTM

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go
File cmd/jujud/bootstrap.go (right):

https://codereview.appspot.com/94700048/diff/1/cmd/jujud/bootstrap.go#newcode145
cmd/jujud/bootstrap.go:145: state.DefaultDialOpts(),
On 2014/05/23 07:07:58, wallyworld wrote:
> On 2014/05/23 06:34:07, axw wrote:
> > I think we also want a longer timeout here, or maybe just a retry loop.
> 
> Not sure. By the time agent.InitializeState() is called, startMongo() with the
> longer timeout has already been called and a connection to mongo established.
So
> here I think it's ok to stick to the default timeout?

Well we have this issue in the tests; we connect, but then get i/o timeouts due
to the machine being under load, and mongo taking too long to respond. And in
fact, the socket timeout is hard-coded in state/open.go right now.

It's probably not likely to happen in reality, so leave it for now.