Feature request - add configurable scheduler random time slew to avoid simultaneous execution scenarios.

[eugenea]

Please make scheduler random slew configurable from scheduler config.
For example slew: 5%. This will be added/substracted to schedule interval to avoid simultaneous execution. THe initial slew for first execution should be 100% (i e random within execution interval).

[basepi]

Sounds good, thanks for the request.

[dangarthwaite]

I took a stab at this during the saltconf sprint in salt/utils/schedule.py:

    class Schedule(object):
            [.... snip ...]
            # Add a random spread% seconds
            spread = int(data.get('spread', 0))
            if spread > 0:
                skew = random.randint(0 , int(seconds * spread / 100))
                log.debug("Spreading {0} seconds by {1} seconds".format(seconds, skew))
                seconds += skew

I think this snippet is being run early and often, resulting in many different skewed values. Someone suggested the calculated skew may need to be persisted in context.

[eliasp]

Until this is implemented, this article outlines various approaches on how to distribute the load across the Salt infrastructure.

[The-Loeki]

I think the current splay covers this? https://docs.saltstack.com/en/latest/ref/states/all/salt.states.schedule.html

splay
The amount of time in seconds to splay a scheduled job. Can be specified as a single value in seconds or as a dictionary range with 'start' and 'end' values.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.