Loading README.md +0 −4 Original line number Diff line number Diff line Loading @@ -90,19 +90,15 @@ You can access the Redis server from the **client** container by following the s ``` docker exec -it client bash ``` 2. Use *redis-cli* command to connect to Redis: ``` redis-cli -h job_cache ``` 3. You can obtain some info about the jobs by searching them on the following queues: - for write operations the queues are *write_pending*, *write_ready* and *write_terminated* - for read operations the queues are *read_pending*, *read_ready* and *read_terminated* 4. Some of the messages sent by the VOSpace REST APIs are handled by the following queues: - for starting async recalls the queue is *start_job_queue* 5. The messages sent by the user command line tools are handled by the following queues: - for vos_data the queue is *data_queue* - for vos_import the queue is *import_queue* Loading Loading
README.md +0 −4 Original line number Diff line number Diff line Loading @@ -90,19 +90,15 @@ You can access the Redis server from the **client** container by following the s ``` docker exec -it client bash ``` 2. Use *redis-cli* command to connect to Redis: ``` redis-cli -h job_cache ``` 3. You can obtain some info about the jobs by searching them on the following queues: - for write operations the queues are *write_pending*, *write_ready* and *write_terminated* - for read operations the queues are *read_pending*, *read_ready* and *read_terminated* 4. Some of the messages sent by the VOSpace REST APIs are handled by the following queues: - for starting async recalls the queue is *start_job_queue* 5. The messages sent by the user command line tools are handled by the following queues: - for vos_data the queue is *data_queue* - for vos_import the queue is *import_queue* Loading
Cristiano Urban <cristiano.urban@inaf.it>Cristiano Urban <cristiano.urban@inaf.it>