You are viewing limited content. For full access, please sign in.

Question

Question

distributed computing how to see unfinished tasks

Distributed Computing Cluster
Updated May 30, 2014
asked on May 23, 2014 • Show version history

I am looking to list all unfinished tasks, I can't see any option to do so. Even if I organize by Job status I only see so many jobs listed to begin with. I also tried the powershell commands

 

Get-dccJob and Get-dccTask

 

Getting the job does't have a parameter to only show unfinished jobs and getting tasks doesn't show any tasks period.

0 0

Replies

replied on May 23, 2014

The only way to check on Task status is through PowerShell. Get-DccJob returns all Jobs submitted within the past three days. If you want to look at a specific Job, use that Job's ID as an argument:

Get-DccJob 10 # Gets info for the Job with ID 10

To filter to several jobs at once, just list the Job IDs:

Get-DccJob 10, 15, 17, 22 # Gets Jobs with ID 10, 15, 17, and 22

If you want to get only unfinished Jobs, use the Where-Object cmdlet (aliased as "where" by default):

Get-DccJob | where { -not $_.IsDone -and -not $_.HasFailed }

Get-DccTask only returns tasks that are currently in progress - they are discarded after they complete. If you have no currently running Jobs, you won't have any Tasks.

 

Out of curiosity, why are you trying to look at the Tasks? Is there a particular troubleshooting scenario where you find it useful?

0 0
View 1 previous reply
replied on May 27, 2014

Is there a way to see older jobs? We are looking to see if there are any jobs still in progress, no matter how old. Last we checked there was jobs running for over 11 days and we were trying to find what happened to those jobs, did they finish or are they still active. The graphic interface was not showing all job history.

0 0
replied on May 28, 2014

Let me clarify on the 3 days point: DCC will show all jobs submitted in the last 3 days, as well as all jobs that are currently running, regardless of the age. Note, however, that after about 3 days the job will fail immediately, as its access token for the Laserfiche server will have expired.

1 1
replied on May 30, 2014

Our jobs are running for over 10 days though.

 

0 0
replied on May 30, 2014

Both of those jobs are definitely indicative of DCC problems. The first one is almost certainly related to an OCR issue that we are aware of and hope to have a fix for in the next release. It should not come up very often, as it is related to OCR itself failing and taking too long to process an image. I'm not sure what is going on with the second job, though. Can you give more details on your setup? How many machines do you have, and what kind of workload are you putting the cluster under? Also, if you could attach the event logs from the scheduler and an affected worker, that would be very helpful in tracking this issue down (note that you would have to save the event logs shortly after the problem occurs, since they are overwritten fairly quickly). It might be useful to open a support case so that we can gather some more information.

0 0
replied on May 27, 2014

Hi Chad,

 

It looks like Matthew's response answered your question! If it did, please click the "This answered my question" button on his post. If you still need assistance with this matter, just update this thread. Thanks!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...