Replica is back, sort of. 94,538 seconds behind master.

---

Replica is back, sort of. 94,538 seconds behind master.

Heck, in just 26 hours it'll be all caught up. :)

Hopefully it'll start cleaning up the backlog of stuff that needs to be purged now. 13.3 million database entries can't be helping server performance.

For the last 90 minutes I'm getting only...

Scheduler request completed: got 0 new tasks

Server can't open database

Project has no tasks available

For the last 90 minutes I'm getting only...

Scheduler request completed: got 0 new tasks

Server can't open database

Project has no tasks available

There were only 300k tasks in the buffer and 250K+ got reported when the servers came back up. Wouldn't be surprised if they simply just got sucked up.

damn

---

I came down with a bad case of i don't give a crap

Well I just uploaded and reported 120 tasks with no problem with the exception of it only verifying about 25 of them and still shows my maximum of 201 work units unreported? Have received about 25 new work units and still says I'm at my maximum allowed hope they show up and not been abducted by aliens

That displaying of the status of the tasks is done by the replica database, which is still some 90,000+ seconds behind on the master database. Once they're somewhat in sync again, will every task show up again.

---

That displaying of the status of the tasks is done by the replica database, which is still some 90,000+ seconds behind on the master database. Once they're somewhat in sync again, will every task show up again.

Well, it went down by 2000 seconds from the last update, and queries from master went up to 7,000. That should even out pretty soon.

which is still some 90,000+ seconds

That's 25 hrs.

---

which is still some 90,000+ seconds

That's 25 hrs.

Doesn't mean it will take that long to sync back up.

which is still some 90,000+ seconds

That's 25 hrs.

Doesn't mean it will take that long to sync back up.

I'd be very pleased if they could do it in 12 hrs.

---

For some reason, a few hours before the weekly outage, results started (finally) to be purged.
However since the outage, that has stopped, and now the number to be purged continues to grow at a steady rate.

---

Grant
Darwin NT

Results waiting to be purged, still heading upwards.

---

Grant
Darwin NT

Results waiting to be purged, still heading upwards.

Yep, 7:10:03 UTC it was 13,823,385, now at 11:20:03 UTC 14,162,579.

Could be 2^32 problem?

And replica is struggling to catch up, sometime ago it was about 62K sec late, now it's back up to 63.8K sec...

I have only 3 out of 9 rigs running right now.
Daily driver dead due to technical issues as yet unresolved.
The other 5 are shut down due to the temps here being around 90f for the next few days, and I don't want the crunchers, the kitties, or myself melting down.

Come on, MSattler and buy a air condition :) My 6kW cooling system is struggling against 14 GPU's :)
I miss your crunching power at WoW, only playing with tbret is not enough :)

Regards
ElricM

---

And replica is struggling to catch up, sometime ago it was about 62K sec late, now it's back up to 63.8K sec...

And bang, at 13:00:03 UTC replica is 47,933 sec behind master.

Something did happend, but will it continue?

Reply to myself:

Yes, it's continuing, now 14:40:03 UTC 25,976 sec behind. So "only" 7.2 hours behind master database....

But as Grant said, results waiting to be purged, still heading upwards

Again, reply to myself.

SSP shows us now that replica is now "on time"

But there is lots if "Burgers" to consume for "db purge: vader"

Anybody see the front page news about the project shutdown this evening till Wednesday morning?

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)