sounds like a scheduler issue
did you try "deadline"?
http://en.wikipedia.org/wiki/Deadline_scheduler
on Linux systems pass "elevator=deadline" as kernel param
Am 12.10.2013 20:58, schrieb Chris McKeever:
> We had a similar issue a bit back - and although it sounds similar - based
> on your foll
We had a similar issue a bit back - and although it sounds similar - based
on your followups it probably isnt, but will just toss this out there
anyhows. We were experiencing connection timeouts when load would ramp up.
Doing some digging we learned that our firewall between the servers
bandwidth
Am 12.10.2013 19:45, schrieb Jørn Dahl-Stamnes:
> On Saturday 12 October 2013 17:36, Reindl Harald wrote:
>> so someone did "optimize table" on a large table
>> you do yourself not a favour restarting the server in such a moment
>
> 7 hours before the server was shut down, we did a alter table t
On Saturday 12 October 2013 17:36, Reindl Harald wrote:
> so someone did "optimize table" on a large table
> you do yourself not a favour restarting the server in such a moment
7 hours before the server was shut down, we did a alter table to add a primary
key to a table that is read-only from the
Am 12.10.2013 17:02, schrieb Jørn Dahl-Stamnes:
> On Saturday 12 October 2013 13:07, Andrew Moore wrote:
>> Could be a crash related to innodb data dictionary being out of sync. Could
>> be a bug.
>
> Seems like a bug yes. However, we had a strange situation yesterday when we
> had several proc
On Saturday 12 October 2013 13:07, Andrew Moore wrote:
> Could be a crash related to innodb data dictionary being out of sync. Could
> be a bug.
Seems like a bug yes. However, we had a strange situation yesterday when we
had several processes in the state "copying to tmp table" (if i remember the
Could be a crash related to innodb data dictionary being out of sync. Could
be a bug.
http://bugs.mysql.com/bug.php?id=55277
On 12 Oct 2013 11:21, "Jørn Dahl-Stamnes" wrote:
> On Saturday 12 October 2013 12:01, nixofortune wrote:
> > You might want to comment
> >
> > bind-address= 12
On Saturday 12 October 2013 12:01, nixofortune wrote:
> You might want to comment
>
> bind-address= 127.0.0.1
>
> in your my.cnf and restart mysql server.
It does not explain why it works under low load and not under high load.
However, I seem to have found something. When I started p
You might want to comment
bind-address= 127.0.0.1
in your my.cnf and restart mysql server.
On 12/10/13 10:49, Jørn Dahl-Stamnes wrote:
Hello,
I got a strange problem related to a production server. It has been working OK
for months, but yesterday it start to fail. There are seve
Hello,
I got a strange problem related to a production server. It has been working OK
for months, but yesterday it start to fail. There are several batch scripts
using the database in addition to a web application using it.
The php scripts running in batch mode began to get:
mysql_connect(): L
10 matches
Mail list logo
