Hocket (Aug 05 2010)


log in

Advanced search

Message boards : Technical News : Hocket (Aug 05 2010)

Previous · 1 · 2
Author Message
Grant (SSSF)
Send message
Joined: 19 Aug 99
Posts: 5831
Credit: 59,396,920
RAC: 47,455
Australia
Message 1023532 - Posted: 7 Aug 2010, 20:21:59 UTC - in response to Message 1023436.

I did wonder at one time whether they were pushing the Informix database to its limits but it appears not, there are larger ones out there.

I think the database limits are mostly hardware. More storage & more RAM would help the databases along considerably.

____________
Grant
Darwin NT.

RoosStar
Send message
Joined: 16 Oct 99
Posts: 48
Credit: 5,796,367
RAC: 7,733
Netherlands
Message 1024206 - Posted: 10 Aug 2010, 15:34:39 UTC - in response to Message 1022928.


Thanks for the update, yet for us non-native-English-tonguers, what's Hocket? (I know Steve Hackett)


In music, hocket is the rhythmic linear technique using the alternation of notes, pitches, or chords. In medieval practice of hocket, a single melody is shared between two (or occasionally more) voices such that alternately one voice sounds while the other rests.

For a more complete explanation see here :D
____________

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 8448
Credit: 4,150,473
RAC: 1,752
United Kingdom
Message 1024371 - Posted: 12 Aug 2010, 22:25:46 UTC - in response to Message 1023436.

One of the rea[s]ons for the new 3 day downtime. I did wonder at one time whether they were pushing the Informix database to its limits but it appears not, there are larger ones out there.

Except that Boinc (s@h) uses the one database for all of the data AND all of the system state changes for all users...

I still wonder if the processing speed of Boinc for a project is limited by the (single threaded) serial updates maximum write speed of the one database log file...


Hang in there Matt and gang!

Happy crunchin',
Martin


____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Josef W. SegurProject donor
Volunteer developer
Volunteer tester
Send message
Joined: 30 Oct 99
Posts: 4252
Credit: 1,050,227
RAC: 244
United States
Message 1024433 - Posted: 13 Aug 2010, 1:44:51 UTC - in response to Message 1024371.

One of the rea[s]ons for the new 3 day downtime. I did wonder at one time whether they were pushing the Informix database to its limits but it appears not, there are larger ones out there.

Except that Boinc (s@h) uses the one database for all of the data AND all of the system state changes for all users...
...
Martin

The BOINC database is MYSQL, and does cover a lot of territory: all of the infrastructure which BOINC provides. The S@H science database, and probably the Astropulse science database, are Informix (though one of the rare Berkeley SETI blog entries mentioned that Eric was thinking of converting to MYSQL for that too).
Joe

Swibby Bear
Send message
Joined: 1 Aug 01
Posts: 236
Credit: 7,276,504
RAC: 48
United States
Message 1025219 - Posted: 15 Aug 2010, 4:14:51 UTC
Last modified: 15 Aug 2010, 4:17:58 UTC

The Server Status Page describes Mork as the Primary BOINC database, with Jocelyn being the replica. But many posts from the admins say that "the replica is down", or "the replica is recovering", yet Mork is said to be the problem child with many untimely crashes (there is never a timely crash, of course). So, for clarification, is Mork being used as the Primary or the Replica?
Thanks

Profile Matt Lebofsky
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar
Send message
Joined: 1 Mar 99
Posts: 1389
Credit: 74,079
RAC: 0
United States
Message 1025625 - Posted: 16 Aug 2010, 17:34:27 UTC - in response to Message 1025219.

Good question. When mork crashes, its relay logs are then in a funny/inconsistent state, which means the replica is unable to work with these relay logs. The easiest way to fix that is to dump the whole database on mork and "recover" the replica from that dump - then everything is consistent again.

- Matt

The Server Status Page describes Mork as the Primary BOINC database, with Jocelyn being the replica. But many posts from the admins say that "the replica is down", or "the replica is recovering", yet Mork is said to be the problem child with many untimely crashes (there is never a timely crash, of course). So, for clarification, is Mork being used as the Primary or the Replica?
Thanks


____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

DJStarfox
Send message
Joined: 23 May 01
Posts: 1043
Credit: 547,682
RAC: 101
United States
Message 1025862 - Posted: 17 Aug 2010, 14:07:36 UTC - in response to Message 1025625.

Good question. When mork crashes, its relay logs are then in a funny/inconsistent state, which means the replica is unable to work with these relay logs. The easiest way to fix that is to dump the whole database on mork and "recover" the replica from that dump - then everything is consistent again.

- Matt


Gosh, Matt, I remember having this problem with MSSQL Server 2k, back in the day. Basically, the company didn't want to buy the enterprise license, so I wrote scripts to perform log shipping manually. After the first catastrophic failure, I changed the scripts to backup the logs to a separate (fast) file server instead. That way, the log backup (on master) and log restore (on replica) can happen asynchronously. Even in the event of master failing, I can resume the logs from the standby from the point of failure. Not sure of the details of MySQL, but this should be possible if you have said file server available. Point is, reading logs from the master directly from the replica has never been robust for me.

Previous · 1 · 2

Message boards : Technical News : Hocket (Aug 05 2010)

Copyright © 2014 University of California