Discussion about retry in state.Open()

[Gustavo Niemeyer]

On Fri, Jan 18, 2013 at 8:20 AM, roger peppe <roger.peppe at canonical.com> wrote:
>> Alternatively, lets just change the retry delay in juju.Conn to 1 second an call it a day.
>
> As I've tried to point out above, the retry delay in juju.Conn is irrelevant.
> In all the live tests I've seen, I've never seen that delay being
> exercised - it's
> a highly unusual corner case.
>
> The right fix is in mgo.

mgo doesn't retry every 250ms.. the original reason for the bug was
purely to slow down the crazy punching and logging to more reasonable
levels.

That said, I agree with David. The level of importance and detail
being given to that problem is over the top. There are conversations
about this for more than *two months*, and this was supposed to be a
trivial bug.

Unless someone wants to propose that trivial branch, there are much
more important things to be doing than fine tuning how fast we connect
(!!!).


gustavo @ http://niemeyer.net