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

Re: When is an openshift master 'up'?



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

On 03/12/2015 03:04 PM, Clayton Coleman wrote:
>> On Mar 12, 2015, at 2:46 PM, Scott Dodson <sdodson redhat com>
>> wrote:
>> 
> 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?
> 
>> Which part of the master?  I think you should put it immediately
>> after the main APIs respond.  The rest of the logic is
>> potentially less important.
> 
>> 90 is incredibly long unless you're generating keys.
>> Unfortunately we at a minimum need to read and check those keys,
>> so I anticipate a small cpu burst for that.
> 
> 
> 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

It
> 
looks like the bulk of the time is in  kubeConfig.RunMinionController()

15:24:44.586985 master.go:107] Started Kubernetes Replication Manager
15:24:44.586992 master.go:115] Started Kubernetes Endpoint Controller
15:26:24.589390 master.go:154] Started Kubernetes Minion Controller


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

iQEcBAEBAgAGBQJVAekJAAoJEMRr2CP2Mq29jREH/icu9SwsjkzoEZWMyltukv8x
UAfFPGJBktRlSPlrOFWvzHEgRpEaroDamMZNBsafhIZRlxubYc9/k+Etcl0BYDfX
+SKpfrSDzD5iTz1WtoTT5KSp880gC7b5Qr/aE5Wp/wdPa90NRgFbiUmw8FLUH2Bb
pvRvFQypvLaeQPE30v5zt44L6IUiZLhkCtJMrDXvPH7SLOThtCK3GwFpx9NJFUP8
F7F2AxzN6MpY4SFnuZrLIGHb1nhG55gE1IZIcUui0TrNmRM192C8R5LLsq1OGpkF
68gb4pCDTngJL5cM6JK3c8lJPs/yz9nPOvXymWHo9LDkJbV3z06Z7zwLq1prcHg=
=moqf
-----END PGP SIGNATURE-----


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