Celery v5.0.5 DocumentationDocumenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 5.0 (singularity) API Reference Internals History Glossary Indices yaml, msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery v5.0.2 DocumentationDocumenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 5.0 (singularity) API Reference Internals History Glossary Indices yaml, msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.1 DocumentationDocumenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 5.0 (singularity) API Reference Internals History Glossary Indices yaml, msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.0 DocumentationDocumenting Tasks with Sphinx Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 5.0 (singularity) API Reference Internals History Glossary Indices yaml, msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you current task get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery 3.0 DocumentationConfiguration and defaults Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.0 (latentcall) What’s new in Celery 3.1 (Cipater) API Reference Internals msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring Scheduling A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you configuration settings get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 DocumentationConfiguration and defaults Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 4.0 (latentcall) What’s new in Celery 3.1 (Cipater) API Reference Internals msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring Scheduling A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you configuration settings get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing Monitoring0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery 3.1 Documentationmsgpack. • zlib, bzip2 compression. • Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you task fails • get a list of people and companies using Celery • write my own remote control command • change worker queues at runtime Jump to • Brokers • Applications • Tasks • Calling 2.2. Getting Started subscribe to worker related events: BROKER_TRANSPORT_OPTIONS = {'fanout_patterns': True} Note that this change is backward incompatible so all workers in the cluster must have this option enabled, or else they0 码力 | 607 页 | 2.27 MB | 1 年前3
Celery 3.1 DocumentationConfiguration and defaults Django Contributing Community Resources Tutorials Frequently Asked Questions Change history What’s new in Celery 3.1 (Cipater) What’s new in Celery 3.0 (Chiastic Slide) What’s new in yaml, msgpack. zlib, bzip2 compression. Cryptographic message signing. Features Monitoring A stream of monitoring events is emitted by workers and is Autoreloading In development workers can be configured a task fails get a list of people and companies using Celery write my own remote control command change worker queues at runtime Jump to ⟶ Brokers Workers Security Contributing Applications Tasks Calling0 码力 | 887 页 | 1.22 MB | 1 年前3
Celery 2.5 Documentationthat inherits from Task. The best practice is to only create custom task classes when you want to change generic behavior, and use the decorator to define tasks. See also: The full documentation on how Chapter 1. Getting Started Celery Documentation, Release 2.5.5 Right now we have to check the worker log files to know what happened with the task. Applying a task returns an AsyncResult, if you have configured client, and not by a worker. logfile The file the worker logs to. See Logging. loglevel The current log level used. hostname Hostname of the worker instance executing the task. delivery_info Additional0 码力 | 400 页 | 1.40 MB | 1 年前3
Celery 2.1 DocumentationReference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 11 Change history 223 11.1 2.1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the task until a worker server has consumed and executed it. Right now we have to check the worker log files to know what happened with the task. This is because we didn’t keep the AsyncResult object returned client, and not by a worker. logfile The log file, can be passed on to get_logger() to gain access to the workers log file. See Logging. loglevel The current log level used. delivery_info Additional0 码力 | 285 页 | 1.19 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













