Celery 2.5 Documentation"CPO CXC 138 46","2.2.4"}, {sasl,"SASL CXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done pluggable, and it comes with three implementations: • inotify (Linux) Used if the pyinotify library is installed. If you are running on Linux this is the recommended implementation, to install the pyinotify software (e.g. celeryd). – sw_ver: Software version (e.g. 2.2.0). – sw_sys: Operating System (e.g. Linux, Windows, Darwin). • worker-heartbeat(hostname, timestamp, sw_ident, sw_ver, sw_sys) Sent every0 码力 | 400 页 | 1.40 MB | 1 年前3
Celery 2.5 Documentation138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done pluggable, and it comes with three implementations: inotify (Linux) Used if the pyinotify library is installed. If you are running on Linux this is the recommended implementation, to install the pyinotify worker software (e.g. celeryd). sw_ver: Software version (e.g. 2.2.0). sw_sys: Operating System (e.g. Linux, Windows, Darwin). worker-heartbeat(hostname, timestamp, sw_ident, sw_ver, sw_sys) Sent every minute0 码力 | 647 页 | 1011.88 KB | 1 年前3
Celery v4.4.5 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1215 页 | 1.44 MB | 1 年前3
Celery 4.4.3 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1209 页 | 1.44 MB | 1 年前3
Celery v4.4.4 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1215 页 | 1.44 MB | 1 年前3
Celery v4.4.6 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1216 页 | 1.44 MB | 1 年前3
Celery v4.4.7 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1219 页 | 1.44 MB | 1 年前3
Celery 4.4.0 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1185 页 | 1.42 MB | 1 年前3
Celery 4.4.1 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1188 页 | 1.42 MB | 1 年前3
Celery v4.3.0 DocumentationCXC 138 11","2.1.8"}, {stdlib,"ERTS CXC 138 10","1.16.4"}, {kernel,"ERTS CXC 138 10","2.13.4"}]}, {nodes,[rabbit@myhost]}, {running_nodes,[rabbit@myhost]}] ...done acks_late is enabled. This behavior is by purpose as… 1. We don’t want to rerun tasks that forces the kernel to send a SIGSEGV (segmentation fault) or similar signals to the process. 2. We assume that a system to automatically restart. 3. A task that allocates too much memory is in danger of triggering the kernel OOM killer, the same may happen again. 4. A task that always fails when redelivered may cause a0 码力 | 1174 页 | 1.41 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













