Forum: CFEngine Help
Subject: Re: cf-exced ignores splaytime on syntax errors / unleash the stampede
Author: [email protected]
Link to topic: https://cfengine.com/forum/read.php?3,24225,24228#msg-24228
I should add, that cf-promises returning an error shouldn't cause cf-execd's
execution to fail... Thats the whole point of splitting off failsafe.cf /
update.cf from one process, then executing promises.cf as a completely separate
process afterwards.
I was under the impression that it was "ok" to have things break under
execution of promises.cf, knowing that failsafe.cf would come along at the
following execution and re-transfer configs over the network that hopefully
were corrected by an administrator.
So, why is cf-promises even being executed in cf-execd? Shouldn't cf-promises
just be executed in cf-agent?
* cf-agent executes against failsafe.cf
** cf-promises validates failsafe.cf
*** cf-agent actually executes
* cf-agent executes against promises.cf
** cf-promises validates promises.cf and all its included policies
*** cf-agent actually executes
Why are we then validating policies during cf-execd startup via cf-promises?
Regardless, that doesn't really matter to me, but, ignoring splaytime in
performing network transfers (regardless of what state promises.cf is in)
sounds like a major bug. It means we don't have automated recovery. We
might as well throw failsafe.cf / update.cf into promises.cf and keep a single
execution if going into a failed state abandons splaytime / breaks network
transfers.
So, if splaytime is busted, does setting the 5m schedule even matter? if 2000
clients are hitting a single master policy server:
60m / 5 = 12 schedule periods
2000 / 12 = 167 clients hitting cf-serverd simultaneously.
At what point does cf-serverd bust? I have in my body server control bundle
logallconnections => "true";
maxconnections => "1000";
But, I doubt this matters. I'm sure cf-serverd has a client limit well before
we hit 1000 machines.
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
