[Spce-user] kamailio-proxy.log error - mysql lost connection

[Matthew Ogden]

Sorry guys, I was actually asking for a more sipwise components answer



I realise with high IO load, things will timeout, but I would assume that
the components of SPCE have a method for dealing with this:

1)      Stop new registrations (without banning unless the frequency is too
high -  a legitimate ban that may have been the cause of highio)

2)      Honour existing registrations

3)      Prioritise call tear downs

4)      Because the thread happens synchronously for call tearups, and
these will be timing out, reply with a 503 or similar code before the final
timeout if unable to log data fast enough. Then log the timeout in waitable
/ (and discardable if necessary) thread?



“Crashing” is not really an option for a SIP server, current calls should
be more important than new calls etc. Current registrations and
re-registrations more important than new ones and so forth.





*From:* Jeremie Chism [mailto:jchism2 at gmail.com]
*Sent:* 28 May 2013 02:54 PM
*To:* Kevin Masse
*Cc:* Matthew Ogden; Martin Wong; spce-user at lists.sipwise.com
*Subject:* Re: [Spce-user] kamailio-proxy.log error - mysql lost connection



What you will see is the load rise then registrations drop and users that
are authorized on the system get banned. Ultimately you will end up with a
drive that is unreadable. This has stopped with sas drives.

On Tuesday, May 28, 2013, Kevin Masse wrote:

Hello, it crashes because the hard drive fails.  Basically it chews up hard
drives in high volume installations without SAS drives at 15k rpm.



This has happened to a few of us in the list the very same way.



Kevin









*Sent from my Verizon Wireless 4G LTE DROID*



Matthew Ogden <matthew at tenacit.net> wrote:

Why does sipwise crash though if its waiting for IO? Surely the call tearup
and teardown should just take longer to initiate?



*From:* spce-user-bounces at lists.sipwise.com [
mailto:spce-user-bounces at lists.sipwise.com<spce-user-bounces at lists.sipwise.com>]
*On Behalf Of *Kevin Masse
*Sent:* 28 May 2013 01:21 PM
*To:* Martin Wong; Jeremie Chism
*Cc:* <Unnamed>
*Subject:* Re: [Spce-user] kamailio-proxy.log error - mysql lost connection



Good morning, SSD’s would not work well in this environment.  SSD’s are
fast but the number of rewrites IO’s and other issues do not make it a
fit.  The burnout rate on the SSD’s is much higher than even the SATA.  The
true answer here is SAS drives at 15K RPM.  They have the longevity and the
speed to avoid issues.



As mentioned earlier with Jeremie, we have learned the hard way about
hardware choices.

Your best choice for configuration would be, SAS drives, in RAID5 with 1
hot spare/swap and 16GB ram or better.



I hope this helps.



Kevin







*From:* spce-user-bounces at lists.sipwise.com [
mailto:spce-user-bounces at lists.sipwise.com<spce-user-bounces at lists.sipwise.com>]
*On Behalf Of *Martin Wong
*Sent:* Monday, May 27, 2013 11:20 PM
*To:* Jeremie Chism
*Cc:* <Unnamed>
*Subject:* Re: [Spce-user] kamailio-proxy.log error - mysql lost connection



Hi guys,



do you think SSD would cut it here? I would like your views on the write
speeds for SSD vs SAS 15K



Thanks

On Tue, M



-- 
Jeremie Chism
Triton Communications
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130528/c0413f2a/attachment-0001.html>