We get more and more cases where we see obsolete information in the monitor. Say, job says its idle, hasn’t picked up any slaves yet, but when you click on it, the task list shows its almost complete already… In some cases, animators already received their ‘job complete’ email notification, but the job is still showing ‘idle’ in the monitor.

Also, the auto refresh can get quite annoying, for example when you are trying to troubleshoot something (or even, just select a bunch of jobs by picking them one by one, holding shift, scrolling. The autorefresh keeps manipulating the list while you are doing your thing…)

Would it be possible to add a ‘definitive’ refresh button that ensures what i am looking at is current?

here is a screenshot example, the job was submitted 14 mins ago, its half finished, but it still shows idle

most of the other jobs around it are also either complete, or rendering, but it just shows ‘queued’

idle_but_not_really.jpg795×285 93.6 KB

Hey Lazslo,
Regarding the auto-refresh ‘manipulating’ the list while you’re looking at it, have you tried disabling Dynamic Sorting on your list panels? That is the feature we put in so that it specifically wouldn’t do that.

At this point, I’m guessing that this must be related to the other issues you guys are seeing, but it could be that we’re just not properly changing the Job’s state when tasks are getting dequeued. We recently made a small change as to how this was done, so it might be that there’s a bug in there somewhere. I’ll investigate this side of things as well.

Either way, I’m not sure that adding a refresh button would help much; either there’s some issues preventing the Monitor from getting the latest data, or the data is incorrect to begin with.

Cheers,

• Jon

Turning off dynamic sorting is a bit of a band aid solution to be honest. Because then i just simply lose sorting altogether. I would keep having to resort manually.

Lets try to figure out the other issues, maybe this will go away when those are solved (mongodb 100% etc)

The job status still does not seem to update for me after a while, even though now the mongo process is below 100% (i shut down ~160 slaves to reduce load).

So i think this issue is unrelated. Last build we were on (beta15) did not have this problem, but beta17 does

Hmm, we’re not able to reproduce this here.

One thing you could try to determine if it’s a separate issue is to install the beta 15 client on your machine, then launch the Monitor from the bin directory (don’t use the Start menu or the Launcher as that will trigger an update). If the Monitor updates data properly, then try installing the beta 17 client back on the machine (don’t use the auto-upgrade) and see if the Monitor has the data update problem again.

Ill try that today. Its affecting multiple people, not just me (not sure if its everyone, but 4-5 people mentioned it)

So far, with beta15, its all updating correctly. Ill try beta17 again, using a fresh install (not a self update)

Cool, thanks for the update. If beta 17 doesn’t work properly after a fresh install, at least we know it’s due to a change between 15 and 17.

Cheers,

• Ryan

With beta17 the problem seems to be back again. Ill give it another go a little while later with beta15

Interesting. I wonder if it has anything to do with the changes we made to handle job deletions better in the Monitor…