• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SETI for BOINC latest news on the migration.

Rattledagger

Elite Member
February 7, 2005
The initial migration of the database to the new server is complete. Tomorrow we will make this new server a database replica. If all goes well it will become the database primary in a few days.
 
They'll do some tests on the new server if everything works as it should, and if no problems they're planning to configure it as a replica-database tonight.

After running it as a replica for a couple of days, and if still no problems, they'll set the new database as master. This should be by the end of the week.

The step afterwards is to optimize the old database and configure this as replica, and most likely run stats and such off the replica so the main should get a little less load. It shouldn't be a problem if this step takes some days, since the new database shouldn't have any problems to handle the load. 😉


Anyway, when the new database is running as it should, they maybe have to throw more hardware at the system for the other processes, like Validator, Transitioner, Splitter, Scheduling-server(s), web-server(s). How long this step eventually will take is unknown...


But, regardless of the servers, they're planning to release the next BOINC core-client including the separate gui in a fortnight. This will mean the software-side have reached "M2 - Decommission old SETI@home". 😎
 
Originally posted by: Rattledagger

But, regardless of the servers, they're planning to release the next BOINC core-client including the separate gui in a fortnight. This will mean the software-side have reached "M2 - Decommission old SETI@home". 😎

Two weeks, eh? Just my luck! I am leaving on Sunday for 17 nights and will be freezing my butt off in NY. Guess that will give my fleet time to empty the queue. Assuming all systems run the whole time I am gone.
 
I wouldn't rush to empty your Q yet Jon 😉

RD

But, regardless of the servers, they're planning to release the next BOINC core-client including the separate gui in a fortnight. This will mean the software-side have reached "M2 - Decommission old SETI@home".

Is this for real? ,if they stick to their plans S@H1 will be killed off in 2weeks?
Seems unlikely considering the other h/w swaps/upgrades they need to do?
 
Originally posted by: Assimilator1
Is this for real? ,if they stick to their plans S@H1 will be killed off in 2weeks?
Seems unlikely considering the other h/w swaps/upgrades they need to do?
I think a fair take on this might be "We'll believe it when we see it" 🙂
And if they do decommission classic in two weeks we will be glad to believe it (when we see it of course 😉)
 
For nearly a year ago there was some re-arrangement in the Taskbase, showing bugs/features to fix/add before:
M1 - Public Launch; M2 - Decommission Old SETI@home; M3 - Other BOINC Projects.
Since the requirement for M2 is the release of the separate gui, and this client is planned released within a fortnight, the BOINC-software will reach this milestone at the same time.

Therefore, "regardless of the servers... the software-side have reached M2" 😉


SETI@home for BOINC have also stated they'll not kill off "classic" before the hardware can handle the load, and with the new db-server "We expect that this will give us the DB performance we need to transition all users from SETI@home Classic to SETI@home BOINC."

Matt Lebofsky posted 12.01.2005:
1. We'll get all servers in place for BOINC that we believe can handle the load
of 500,000 new users. We're talkin' various web servers, data servers,
databases, etc.. This is happening right now.

2. We'll send out a mass e-mail asking all old SETI@home users (active or
otherwise) to consider moving over to BOINC. As well, we'll post information on
the home page about transferring to BOINC. In these e-mails/posts we'll have a
clear cut-off date (probably at least a month in the future, if not two) when
SETI@home classic will stop working altogether.


Don't know if the hardware is ready, but expects v4.2x is released this month. 🙂
 
From Technical News:
February 9, 2005 - 23:30 UTC
Server status update: The new database server is still being tested, but is working quite well. We're fairly convinced at this point that the crash last week was due to a bug in gnome (a unix windowing system), which has since been disabled.

Once we switch over, it may be impossible to switch back (as it will be much faster than our current database server). So we're being extra cautious, adding queries one by one and checking their success. We have no set time for the transition, but barring any catastrophe it should be any day now.
 
That's clearer🙂

Btw ,when they kill S@H1 do you think they'll stop sending off WUs 1st & let it die off as people run out of WUs?, or just stop it dead in its tracks regardless of the WUs 'out in the field' ?
Any info on that?
 
Don't know...

But, since a user is active if returned anything the last 4 weeks, my solution would have been to kill wu-distribution 1st... If Berkeley uses the same method, no idea.
 
Back
Top