-
Notifications
You must be signed in to change notification settings - Fork 14
Internal threads
Paul Nilsson edited this page Jul 19, 2022
·
1 revision
The Pilot uses a number of internal threads to keep track of different tasks. They are listed and explained below.
Thread name | Controller | Usage |
---|---|---|
data | generic | Main thread for data control (generic workflow). |
copytool_in | data | Stage-in thread. |
copytool_out | data | Stage-out thread. |
queue_monitoring | data | Thread for monitoring queues. .. |
receive | interceptor | (Deprecated) |
send | interceptor | (Deprecated) |
job | generic | Main thread for job control. (generic workflow). |
validate | job | .. |
retrieve | job | .. |
create_data_payload | job | .. |
queue_monitor | job | .. |
job_monitor | job | .. |
fast_job_monitor | job | Thread providing fast monitoring which could be useful for real-time logging. It calls |
user defined fast_monitor_tasks(). | ||
message_listener | job | Listener for ActiveMQ messages. |
payload | generic | Main thread for payload control (generic workflow). |
validate_pre | payload | .. |
execute_payloads | payload | .. |
validate_post | payload | .. |
failed_post | payload | .. |
run_realtimelog | payload | .. |
monitor | generic | Main thread for monitor control (generic workflow). Currently this thread does not spawn |
any further threads. | ||
job | stager | Main thread for job control (stager workflow). |
data | stager | Main thread for data control (stager workflow). |
monitor | stager | Main thread for monitor control (stager workflow). |
- Introduction
- Pilot Architecture
- Pilot Workflows
- Event service
- Metadata
- Direct Access
- Signal Handling
- Error Codes
- Containers
- Special Algorithms
- Pilot Configuration
- Timing Measurements
- Copy Tools
- Pilot release procedure