# Job Transit To Another Node

**URL:** <https://community.openpbs.org/t/job-transit-to-another-node/3863>\
**Category:** Users/Site Administrators\
**Created:** [May 9, 2024, 11:23am UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863 "2024-05-09T11:23:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wakaka](https://avatars.discourse-cdn.com/v4/letter/w/d07c76/32.png) [@wakaka](https://community.openpbs.org/u/wakaka)\
**Post date:** [May 9, 2024, 11:23am UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/1 "2024-05-09T11:23:12Z")

</div>

When a job is runnning on a node, how can I transit it to another node?  
Hope for an answer.  
Be deeply greatful.

---

<div class="post-metadata">

**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\
**Post date:** [May 11, 2024, 5:34pm UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/2 "2024-05-11T17:34:55Z")

</div>

The running jobs (job is in R state) on a compute node cannot be moved to another node.

If that node running that job gets disconnected from the PBS Server, then the job will be automatically requeued on to another node by PBS Server after 310seconds. The server attribute is node\_fail\_requeue.

Reference: RG-290, PBS Professional 2022.1 Reference Guide

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/pbspro/original/1X/74803b27b01a43ab63f39a40bbf02ab9ee4180f5.png)

---

<div class="post-metadata">

**Author:** ![wakaka](https://avatars.discourse-cdn.com/v4/letter/w/d07c76/32.png) [@wakaka](https://community.openpbs.org/u/wakaka)\
**Post date:** [May 13, 2024, 12:55pm UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/3 "2024-05-13T12:55:06Z")

</div>

But how can the PBS Server know a job is rerunable or not?  
How does it judge？

---

<div class="post-metadata">

**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\
**Post date:** [May 13, 2024, 6:57pm UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/4 "2024-05-13T18:57:29Z")

</div>

> [@wakaka](#):
>
> But how can the PBS Server know a job is rerunable or not?

qstat -f | grep -i Rerunable

Please refer the PBS Professional 2024.1 Reference Guide RG-227

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/pbspro/original/1X/c9a690945e6fb075bc47f87ba0aaa882fd684b0b.png)

---

<div class="post-metadata">

**Author:** ![wakaka](https://avatars.discourse-cdn.com/v4/letter/w/d07c76/32.png) [@wakaka](https://community.openpbs.org/u/wakaka)\
**Post date:** [May 14, 2024, 12:29pm UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/5 "2024-05-14T12:29:56Z")

</div>

So, whether the job can be rerun is entirely determined by the job submitter or user.

---

<div class="post-metadata">

**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\
**Post date:** [May 14, 2024, 2:48pm UTC](https://community.openpbs.org/t/job-transit-to-another-node/3863/6 "2024-05-14T14:48:49Z")

</div>

Yes, by default all jobs are rerunable ( except interactive jobs).  
If the user does not want it to be reruannable, the user can opt out using -r n wihle submitting the job using qsub.