ter-long-semaphore-waits-mysql-becomes-unresponsive
Same problem here... happens about once a month, since recent MySQL version
update
http://qnalist.com/questions/4209635/after-long-semaphore-waits-mysql-becomes-unresponsive
- Original Message -
> From: "Rik Wasmus"
>
> A plugin what for? Also time, money, effort. I didn't get hired as a
> MySQL-plugin writer here, and my list of pet-projects for my personal time
> is rather full at the moment :)
For keeping track of various interesting variables like query
On 2011-05-25 12:24:37 you wrote:
> > Cacti does store a lot of things by snmp, that's the way I know
> > memory, CPU usage & average load never showed a hitch, all's well
> > according to the OS, only MySQL is slowly dying...
>
> So what stops you from writing MySQL plugins? Probably plenty out t
- Original Message -
> From: "Rik Wasmus"
>
> Cacti does store a lot of things by snmp, that's the way I know
> memory, CPU usage & average load never showed a hitch, all's well according to
> the OS, only MySQL is slowly dying...
So what stops you from writing MySQL plugins? Probably pl
On 2011-05-24 18:25:07 Johan De Meersman wrote:
> > OK, but that would mean that the answer to the question:
> >
> > "I may be wrong here, but I tend to interpret this as
> > '140054029002496' is trying to get an exclusive lock on 0x78733f8, on
> > which it already has an exclusive lock, and hence
- Original Message -
> From: "Rik Wasmus"
>
> OK, but that would mean that the answer to the question:
>
> "I may be wrong here, but I tend to interpret this as
> '140054029002496' is trying to get an exclusive lock on 0x78733f8, on which
> it already has
> an exclusive lock, and hence
On 2011-05-24 16:30:13 you wrote:
> > 2 simultaneous queries with the same thread-id? Is that possible?
>
> No, not with the same thread-id. Deadlock occurs when two threads attempt
> to lock the same resources, but do so in an order which causes both sides
> to hold part of the resources the othe
- Original Message -
> From: "Rik Wasmus"
>
> 2 simultaneous queries with the same thread-id? Is that possible?
No, not with the same thread-id. Deadlock occurs when two threads attempt to
lock the same resources, but do so in an order which causes both sides to hold
part of the resour
> > I may be wrong here, but I tend to interpret this as '140054029002496' is
> > trying to get an exclusive lock on 0x78733f8, on which it already has an
> > exclusive lock, and hence is deadlocked in some manner. Am I right
> > there? How can this happen?
>
> I'm not too hot on the internals, b
- Original Message -
> From: r...@grib.nl
>
> I may be wrong here, but I tend to interpret this as '140054029002496' is
> trying to get an exclusive lock on 0x78733f8, on which it already has an
> exclusive lock, and hence is deadlocked in some manner. Am I right there? How
> can this hap
Hi all,
yesterday the mysql process on a database server became totallly unresponsive
after some long semaphore waits (load/cpu/memory were OK, as were all other
processes). The debug output started with this:
InnoDB: Warning: a long semaphore wait:
--Thread 140054029002496 has waited at /btr/b
12 matches
Mail list logo
