Insta-Purge

Well, it has been around 12 hours since the last set of repairs to the project, and everything still seems to be just as snappy as it was after the last backend restart. The server status looks like the backend is holding its own as well.

So can we get off insta-purge and go back to something a little more user friendly?

I would suggest 12 hours to start with. Since you increased the in progress quota by 50%, decreasing the purge interval by the same amount from what it was before the disaster would seem to be appropriate.

Of course, this is assuming that the patch to allow less than whole day purge increments wasn't part of the problem after the big meltdown. ;-)

Alinator

It seems to be stable again. Atleast up it in increments if needed, 1 hour, 3, 6, 12, 24. 6 would be the minimum I want to check on results 24-48 is preferrable.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

I'm still tracking down the leaky workunit issue. So it'll be on insta-purge until I figure that out. Afterwards i'll start increasing it and see how the server handles it.

---

Use a stick of gum and plug the hole! ;p

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

I'm still tracking down the leaky workunit issue. So it'll be on insta-purge until I figure that out. Afterwards i'll start increasing it and see how the server handles it.

OK...

If it helps, I have a Zombie on 20335 and 23908.

You're on your own for the stealth ones! ;-)

Alinator

Seems like my laptop is somehow involved in this.

Laptop has many units assigned to it that have not been reported back, but they are not on my system. They will time out and expire. Wonder what is happening here?

I noticed that it seems to happen when I am asleep in the early morning.

---

Never surrender and never give up. In the darkest hour there is always hope.

Here's some leaker's for you 7933 and 7968 found on my task list and not purged yet...strange.

I have quite a few from 8 Feb 09 still showing up. Task IDs/Result IDs 2911 to 2923, 2953 to 2956 and 15663, 15664, 15672 and 15675.

Please quite a few from 9 Feb as well.

Hmmm...

Due to pilot error, I allowed a couple of my hosts which aren't currently supported to contact the project and they downloaded. Since they would have all errored out anyway, I aborted the tasks.

Interestingly, this seems to have resulted in the WU's becoming Zombified. A number of them have been reissued, run, returned, and validated, yet remain unpurged hours later.

So it appears when a WU goes to extra replications, the DB loses track of the WU state, at least as far as flagging it for purging purposes.

Alinator

Hmmm...

Due to pilot error, I allowed a couple of my hosts which aren't currently supported to contact the project and they downloaded. Since they would have all errored out anyway, I aborted the tasks.

Interestingly, this seems to have resulted in the WU's becoming Zombified. A number of them have been reissued, run, returned, and validated, yet remain unpurged hours later.

So it appears when a WU goes to extra replications, the DB loses track of the WU state, at least as far as flagging it for purging purposes.

Alinator

I think i found it. These weren't having a result set as canonical, so for whatever reason, that would make their transition time += 10 days. I think this was the cause of the zombies.

---

Hmmm...

Due to pilot error, I allowed a couple of my hosts which aren't currently supported to contact the project and they downloaded. Since they would have all errored out anyway, I aborted the tasks.

Interestingly, this seems to have resulted in the WU's becoming Zombified. A number of them have been reissued, run, returned, and validated, yet remain unpurged hours later.

So it appears when a WU goes to extra replications, the DB loses track of the WU state, at least as far as flagging it for purging purposes.

Alinator

I think i found it. These weren't having a result set as canonical, so for whatever reason, that would make their transition time += 10 days. I think this was the cause of the zombies.

LOL...

Yes, all of my Zombies have gone poof. :-)

Funny you should mention the part about no canonical being shown. I was going to ask about that, but figured you left it out on purpose when you integrated the validator and assimilator (give self slap on head). ;-)

Next time I see something like that I will mention it right away, instead of being stupid! Sheesh... I've been playing this game since before they even called them PC's. You'd think I'd know better than that. :-D

Alinator

I think i found it. These weren't having a result set as canonical, so for whatever reason, that would make their transition time += 10 days. I think this was the cause of the zombies.

Yep, all gone!

OK...

What I'm noticing now from my end is that a canonical result is shown for completed tasks, but the Granted Credit shows as zero in the WU info section, even though it displays the granted credit in the detail section of the WU summary page.

Alinator

OK...

What I'm noticing now from my end is that a canonical result is shown for completed tasks, but the Granted Credit shows as zero in the WU info section, even though it displays the granted credit in the detail section of the WU summary page.

Alinator

Think i fixed this just now.

---

Yep, everything looks OK from here.

Alinator

Since the probs seem to be solved it would be nice if insta-purge is converted to say in-an-hour-purge to start with. Or are we not there yet?

Since the probs seem to be solved it would be nice if insta-purge is converted to say in-an-hour-purge to start with. Or are we not there yet?

I've fixed most the zombie WU problem but not quite sure if it's all fixed yet.

---

Shouldn't that be enough to extend the time to atleast an hour?

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Shouldn't that be enough to extend the time to atleast an hour?

It makes it a lot harder (or impossible) to tell if the WUs I'm looking at in the database are ones that will be deleted after the hour or not at all.

With the insta-purge, if something sticks around I know it's problematic.

---

Shouldn't that be enough to extend the time to atleast an hour?

It makes it a lot harder (or impossible) to tell if the WUs I'm looking at in the database are ones that will be deleted after the hour or not at all.

With the insta-purge, if something sticks around I know it's problematic.

And are you still seeing things hanging about?

---

I am the Kittyman.

Please visit and give a Click for Seti City.