Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi,

we're currently running a larger SQL database backup, which exceeds the currently allowed amount of parallel connections.

Given that SQL right now uses about 30 GB (!) of RAM, I can't extend the number of allowed connections further right now, so we have to wait until the backup is finished. (It's 10:30 pm here, but I'm awake for a while, so if it lasts too long, I will kill it to bring back the website.)

Mid-term solution is to get stronger hardware, or at least put the SQL server on a different machine. I'm still looking into what is causing the high load. We know since when the problems occur, but sadly, it's not clear what _what_ causes the high load - the database size seem to have grown massively, and first investigations look like Piwik is using it heavily. I will check with Cloph to see if that is true.

Note that neither internal nor external e-mails, nor mailing lists, nor the download per se is affected.

Sorry for the inconveniences,
Florian

--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.