| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: [Completed] Extended BOINC Server Outage Planned from 21:30 UTC Jan 13 thru 8:00 UTC Jan 14th |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 76
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Duplicating this post from Known issues for some talk on this longer outage, and to spur a few more reads, which so far is low if not poor [by my standards]
----------------------------------------We are going to be upgrading our database for the BOINC systems from MySQL 5.0 to MySQL 5.5. There have been substantial improvements in the MySQL database performance between these releases, and as we continue to grow, we need this additional performance. In order to accomplish this change, we will need to stop all access to the BOINC database during this change. This will allow us to take a clean backup of the database and then upgrade the system. Due to the size of the database, we expect it to take some time to do this upgrade and thus the length of the outage. During the outage the website and forums will work (except for the result status page which queries the BOINC database). Additionally, clients will be able to update result files and download input files. However, clients will not be able to communicate with the server to report completed results nor obtain new work to process. Additionally, this change window occurs during the end of day statistics process. We will defer the end of day statistics process until after the database upgrade is complete. We apologize for the disruption, but it is necessary to support the continued growth in your contribution. thanks. knreed [Jan 10, 2012 11:00:57 PM] Have replicated this post also to the Berkeley project outage thread and am in expectation to see it also appear in the 6.12+ client Notices tab, so volunteers get alerted to bulk up a bit, should they be running on low buffers. The bit in Kevin's message I did not fully understand was bolded [he may want to post a little expansion in this thread]. Reporting work is not much of a concern, but what are these input files and update of result files? Did he mean output files [the once you see in the client transfer tab as phase one of the Result reporting?] Certainly, what I'm planning to do is set work fetch to *No* so there wont be attempts to backfill the cache and on Saturday check out the news. With the additional buffer at 1.75 days got a safety set, in case Murphy pays a visit, and wont get stuck in the rush that surely will occur when the gates open again... will try uploading later after the connect Tsunami recedes. Kevin and team: Good luck! --//-- edit: Once clarified, I'll probable set my client to suspend networking. Doing WCG only anyhow, well 99% of the time. [Edit 4 times, last edit by Former Member at Jan 14, 2012 10:29:04 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
A couple of things are not clear to me:
1] Will a cruncher be able to upload done-WUs and/or download to-be-crunched-WUs during the outage? 2] When (in date and hours:minutes) is the stats expected to be back to normal? ; |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Point one, part 2 is answered: No.
Point one, part 1 was already queried. The result files [output], if could be uploaded. "Ready to Report" will not be possible to clear as the scheduler will be off... the same scheduler that administers the assignment of new work... The key in this is "we will need to stop all access to the BOINC database during this change". --//-- |
||
|
|
LCB001
Advanced Cruncher CANADA Joined: Oct 14, 2009 Post Count: 69 Status: Offline Project Badges: 
|
Thank you for the timely reminder Mr. SekeRob, while I try to keep current on the latest posts I had missed/forgotten this one.
----------------------------------------Really appreciate the time you dedicate to your charts and this site overall...  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Additionally, clients will be able to update result files and download input files. This part was not clear to me. I have a vague idea of what those files/files are.However, clients will not be able to communicate with the server to report completed results nor obtain new work to process. This part was clear to me initially, but I wanted confirmation.In my search for confirmation, I first re-read the original message by knreed, and I, perhaps inadvertently, next associated update result files and report completed results on the "upload" side of M2M (machine-to-machine) communication on one hand, and on the other hand download input files and obtain new work to process The response of CA SekeRob, clarified the upload/download of WUs and that is good enough for me although the expected date-time resumption of the stats is still unclear to me and I guess that I'll pass up that stats thing for now. Going forward, I'm still curious what those files/files are. ; |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 3010 Status: Offline Project Badges: 
|
the expected date-time resumption of the stats is still unclear to me I'm reading this to mean that, as soon as the change is complete and verified, then they'll kick off the stats process. Thus, we'll only find out when the change is totally complete (it may "look" complete from where we're standing - but there may be a lot more actions to do in the background), when the Stats process has been started.Obviously, one of the many items on the timeline, will be to post a completion notice on the forum - and, again, only time will tell when that's able to be posted. Basically, as with any complicated process, things can unexpectedly go wrong/take a lot longer than planned etc., Likewise, things can run faster than anticipated - and thus, changes can be completed faster than originally estimated. So, really, I don't think that there's going to be an answer to this until approx. 08:00 UTC on the 14th of Jan 2012.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well said, gb009761. You have a fine reading of things! So, let the outage begin... Oops, not so fast right there, we do have a schedule to follow on the dot. I'm stocking up on WUs now
 . |
||
|
|
Mysteron347
Senior Cruncher Australia Joined: Apr 28, 2007 Post Count: 179 Status: Offline Project Badges: 
|
Got to admit I find the terminology confusing, but what I gather is that the administrative functions (password/email changes etc) will still work, as will the website, forum and software downloads, but anything to do with new or returned workunits or statistics will be suspended.
I'd suggest that it would only be the eternal optimist who'd expect everything to go as planned. Starting the operation on Friday the 13th would seem to be sending a gilt-edged invitation to and laying out the red carpet for Mr. Murphy. I'll just make sure to fill the buffer....Oh - no need - big buffers rule! |
||
|
|
BSD
Senior Cruncher Joined: Apr 27, 2011 Post Count: 224 Status: Offline |
I'm stocking up on WUs now +1 I upped my cache to 2 days of yummy crunchies  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@Mysteron347,
Got to admit I find the terminology confusing, but what I gather is that the administrative functions (password/email changes etc) will still work, as will the website, forum and software downloads, but anything to do with new or returned workunits or statistics will be suspended. Why do the Anyways, from what I can read, the upload process may proceed, only that the "Ready to Report" will not work -- for this would obviously require querying the database which would be busy being worked on, while the upload part should still work as this part only takes 'dumping the raw results' for review later and does not have to query the database at the time of upload. The logic there did appear to me to also must work for the download process as well, but apparently not, not from the server's point-of-view anyway. Why that is the case for the download process, I surmise, is that while the download of the new WUs can be 'dumped' to the cruncher, the new WUs are not yet in the existing database (but have to be included) before releasing the new WUs. Because the database is involved in all parts of the download process, any and all parts of the download process will have to be suspended. That as much is now clear to me. As for other functions (including administrative functions), they may still be affected to some extent depending on what is tied up to querying the database and the nature of that connection (casual, normal, important, critical, top-secret, etc). Want to strike off the devils? Then stocking up on WUs is relatively simple with only a few devils, if ever ! ; |
||
|
|
|