# Ray submission queue

**URL:** <https://discuss.ray.io/t/ray-submission-queue/1580>\
**Category:** Kubernetes\
**Created:** [April 6, 2021, 7:17pm UTC](https://discuss.ray.io/t/ray-submission-queue/1580 "2021-04-06T19:17:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blublinsky](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@blublinsky](https://discuss.ray.io/u/blublinsky)\
**Post date:** [April 6, 2021, 7:17pm UTC](https://discuss.ray.io/t/ray-submission-queue/1580/1 "2021-04-06T19:17:10Z")

</div>

If I am trying to submit more remote jobs then available resources, then my understanding is that those remote jobs are queued up for execution, correct?  
What is the practical limit for the submission queue? Do I have any visibility into it? Is there an option to somehow persist it, if the cluster goes down and restarts? In other words, what are the guarantees that Ray provides on such queue?  
Also, once submitting a a remote job, can I disconnect and come back later to see the state in the queue and results, if the job has executed?

---

<div class="post-metadata">

**Author:** ![Dmitri](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/dmitri/32/657_2.png) [@Dmitri](https://discuss.ray.io/u/Dmitri)\
**Post date:** [April 7, 2021, 2:12am UTC](https://discuss.ray.io/t/ray-submission-queue/1580/2 "2021-04-07T02:12:04Z")

</div>

These are great questions – I think the linked thread is a good place to discuss things on the theme of job queues:

> [@Job Queue in Ray?](https://discuss.ray.io/t/job-queue-in-ray/1139):
>
> For larger amounts of tasks to be processed, it seems like it would be a good fit to have some kind of job queue, from where tasks are assigned to workers or workers eat from the Queue. In particular, this seems to be useful for handling error scenarios, retries, etc. in a robust fashion. Is there anything like that envisioned for Ray?