[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

When is an openshift master 'up'?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I contributed systemd notification support[1] a few weeks back which
prevents systemd from marking a service as having started until that
process sends a notification that it's finished. This allows systemd
to delay dependencies until their requirements are met, ie:
openshift-sdn-master doesn't attempt to start until openshift-master
is done.

With more recent builds it's taking longer than the 90 second default
for openshift master to send the notification that it has been
started. I'm going to go ahead and increase that timeout to 300s for
the time being. But I'm wondering if the startup notification can be
moved earlier in startup sequence?

Aside from that, what's the upper bound for how long we should expect
starting openshift master to take?

For anyone interested, here[2] is the startup logs running on my
laptop, SSD, plenty of memory, etc.

1 - https://github.com/openshift/origin/pull/1204
2 -
https://gist.githubusercontent.com/sdodson/d213d98c08ff832ddb0b/raw/a970277c50c2088738299bf3ff10b135c67e8e45/gistfile1.txt

- --
Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJVAd7lAAoJEMRr2CP2Mq29ZTYH/jeln170rQhZ41GOJRqbmC0F
spv5s6FadZ1uXB4ymERzGLUN5YhB02GYlSUsd8AFyYGVFH+iNUX9w7BOmUROR4gF
9UeWjF/i4ZRfXNjzfffH340bkY8HGKH74rJaahroFEBGUF59tIumtw4q6venBO+j
sqxSZUGk5MTn1vwx9PMsu0ozeemi1JoE5MV+PV6IFEeeJ/TFUZGpIBN1d8HTHk4t
FBuo035H5ikOdDeXN+g3Nicq2zUt3w9ID/BwVk9Yq1en+fkI7rtsMviVQFeTXMU2
EN/SQnBomacI8JQiYPuKcEhghooRdab2qp6b62y92RqpnM8+S926V4BTvpeg7Y8=
=AlXB
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]