Failfast / don't fail starting

[Cantor, Scott]

On 1/9/14, 1:15 PM, "Christopher Bongaarts" <cab at umn.edu> wrote:
>
>The main "use case" (or maybe better termed "gripe about idp2") is a
>situation where you have shut down your LDAP and IdP servers (say, for
>yearly data center maintenance), and the IdP starts up faster than the
>LDAP service.  Ideal behavior: IdP begins startup, but fails requests
>involving LDAP until a working connection is established.  Current
>behavior:  IdP explodes violently and must be restarted by hand.

Default, yes. I ported the non-failfast version of the pooling code I
wrote back into 2.4.0.

My personal opinion is that the default should not be fail fast for
connectivity, irregardless of the defaults elsewhere, but I will say that
Paul's issue applies just as much to the LDAP case because there many
deploys where the LDAP usage is not core, but optional and doesn't always
come into play. So the point is whether you know there's a problem at
startup or after startup. Some people like that, and some don't.

-- Scott