...
- Request 529712 couldn't be canceled because it had already finished by the time the service received the cancellation command.
- Request 529713 was canceled while it was still sitting in the input queue and before it even started.
- Request 529714 was canceled before the service began reading the input file.
- Request 529715 got canceled before loading the content of the temporary file into MySQL. Note that the amount of data that was about to be ingested into MySQL should be already known at this stage (see attributes num_bytes and num_rows).
Status of the contribution requests in the scope of a transaction
Due to its inherent efficiency, this is the recommended way of tracking the progression of the asynchronous requests by the workflows.
This is another group request that is similar to the above-described group cancelation request. This request would pull the status of all contributions submitted to the given worker service in the context of the specified transaction. Here is an example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
http://lsst-qserv-db03:25004/ingest/file-async/trans/45 -X GET -H 'Content-Type: application/json' \
-d'{"auth_key":"CHANGEME"}' |
The service returns a result that has the same schema as the one the group cancelation one.
Resuming outstanding requests after restarting workers
...