# Forcefully cancel running / queuing job

**URL:** <https://community.dremio.com/t/forcefully-cancel-running-queuing-job/4896>\
**Category:** Uncategorized\
**Created:** [January 16, 2020, 7:44am UTC](https://community.dremio.com/t/forcefully-cancel-running-queuing-job/4896 "2020-01-16T07:44:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chafidz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/chafidz/32/1267_2.png) [@chafidz](https://community.dremio.com/u/chafidz)\
**Post date:** [January 16, 2020, 7:44am UTC](https://community.dremio.com/t/forcefully-cancel-running-queuing-job/4896/1 "2020-01-16T07:44:25Z")

</div>

Is there any non-brutal way like restarting dremio service on the master to forcefully (and gracefully) cancel or removing currently running or queuing jobs from the job list for whatever reason?  
For example, a user executed a query that blocking dremio executor i/o which prevented or make the next query running on snail speed.  
Or when somehow, the jobs just vanished from the coordinator and stuck on the list because the master doesn’t know whether the job is running, canceled, or encountered an error.  
Etc.

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [January 17, 2020, 12:27am UTC](https://community.dremio.com/t/forcefully-cancel-running-queuing-job/4896/2 "2020-01-17T00:27:38Z")

</div>

@chafidz

In newer versions of Dremio, job cancelation is more consistent. What version of Dremio are you on?

---

<div class="post-metadata">

**Author:** ![chafidz](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/chafidz/32/1267_2.png) [@chafidz](https://community.dremio.com/u/chafidz)\
**Post date:** [January 22, 2020, 2:33am UTC](https://community.dremio.com/t/forcefully-cancel-running-queuing-job/4896/3 "2020-01-22T02:33:56Z")

</div>

Sorry for the late reply.  
We’re currently using v3.3.2 and still deciding which v4.x we will upgrade.
