beat.web.scripts.scheduler module

Starts the scheduling process.

Usage:
%(prog)s [-v … | –verbose …] [–settings=<file>] [–interval=<seconds>]

[–address=<address>] [–port=<port>]

%(prog)s (-h | –help) %(prog)s (-V | –version)

Options:
-h, --help

Show this help message

-V, --version

Show program’s version number

-v, --verbose

Increases the output verbosity level

-S <file>, --settings=<file>

The module name of the Django settings file [default: beat.web.settings.settings]

-i <seconds>, –interval=<seconds> The time, in seconds, in which this

scheduler will try to allocate job splits to existing workers. If not set, use the value available on the Django settings file, at the variable SCHEDULING_INTERVAL.

-a <address>, --address=<address>

The address to which the processing nodes must establish a connection to

-p <port>, --port=<port>

The port to which the processing nodes must establish a connection to

Examples

To start the scheduling process do the following:

$ %(prog)s

You can pass the -v flag to start the scheduler with the logging level set to INFO or -vv to set it to DEBUG. By default, the logging level is set to WARNING if no -v flag is passed.

beat.web.scripts.scheduler.onWorkerReady(name)[source]
beat.web.scripts.scheduler.onWorkerGone(name)[source]
beat.web.scripts.scheduler.remove_split_id_from(list, split_id)[source]
beat.web.scripts.scheduler.main(user_input=None)[source]