- Original Message -
From: Hiromichi Watari hiromichiwat...@yahoo.com
I created Parallel Universe which is a MySQL 5.5 compatible server
with fast query execution.
Speed is achieved by the new patent pending technology which utilizes
multi core/CPU of server hardware.
Just like
Ok... I have one of those pesky error, in an application not handling
deadlocks or lockwaits.
The database object can't be modified to support deadlock/lockwatis...
I can only change database parameteres
Database info: Server version: 5.5.22-log Source distribution
from show engine innodb
On Thu, May 10, 2012 at 10:26 PM, Steven Staples sstap...@mnsi.net wrote:
I think you can scan the syslog for the mysql daemon, and it will show you
any crashed, or problematic tables?
If this is in fact the case, you could try that, and then run though the
tables to check them later?
Hi all
last night we droped some partitions and we found that the first drop
costs about 30mins and then it's about 3 seconds.
when droping the partition all processes are shown waiting for opening
table like:
Hi all.
Is there a possibility to see the info from slowlog somewhere in database?
I would like to see slow queries using mysql and not by watching the log
file.
I've searched on google and mysql website but hasn't found the solution.
Best regards,
Rafal Radecki.
Hi Rafal,
If you are using MySQL 5.1 and later version than you can enable the log
tables and you can see slow queries in the log tables.
Please check this post:
http://nilinfobin.com/2012/03/slow_log-and-general_log-tables-in-mysql-5-1/
regards,
Nilnandan
On Fri, May 11, 2012 at 2:40 PM, Rafał
On 11/05/2012 07:57, Johan De Meersman wrote:
- Original Message -
From: Hiromichi Watarihiromichiwat...@yahoo.com
I created Parallel Universe which is a MySQL 5.5 compatible server
with fast query execution.
Speed is achieved by the new patent pending technology which utilizes
multi
What are the VARIABLES values of
open_files_limit
table_open_cache
table_definition_cache
How partitions in this table? How many tables in your system?
-Original Message-
From: louis liu [mailto:yloui...@gmail.com]
Sent: Friday, May 11, 2012 1:35 AM
To: mysql@lists.mysql.com
Deadlocks and lock wait timeouts are independent of one another. A
deadlock happens when there is a cycle in the waits-for graph. Your
transactions are *active* for 132 and 33 seconds, but the deadlock
happens at the instant the conflict is detected, not after waiting. A
deadlock cannot be
Much faster: SHOW TABLE STATUS -- It will have NULLs for the tables that
really need REPAIR. (Those that were not properly closed don't have to be
REPAIRed.)
If you system is new enough, you can find the list of databases (TABLE_SCHEMA)
from `information_schema`.
In the long run, consider
open_files_limit =3
table_open_cache =4096
table_definition_cache =256
How partitions in this table?
14 partitions
How many tables in your system ?
about 390 tables
cheers
2012/5/11 Rick James rja...@yahoo-inc.com
What are the VARIABLES values of
open_files_limit
table_open_cache
If you have 14 partitions in each of 390 tables, and if you have most of the
tables 'active', then you are possibly thrashing in the table_open_cache.
Compute (SHOW STATUS):
Opened_tables / Uptime -- don't want more than a few per sec.
Opened_files / Uptime -- ditto
Opened_table_definitions /
Ok, so I had a deadlock...
But then, why a deadlock doesn't rollback all the transaccion?
On Fri, May 11, 2012 at 9:55 AM, Baron Schwartz ba...@xaprb.com wrote:
Deadlocks and lock wait timeouts are independent of one another. A
deadlock happens when there is a cycle in the waits-for graph.
Hello Andrés
did you notice that both transactions are trying to update records with
same *accountid='3235296' *
and that they lock the same index page? *space id 5806 page no 69100 n bits
176 index*
Cheers
Claudio
2012/5/11 Andrés Tello mr.crip...@gmail.com
Ok, so I had a deadlock...
But
Yup, but a far I understand...
I made a
select balance for update where accountid=3235296 lock in shared mode;
over the same accountid , so the second transacion just would need to wait
to the first transaccion to finish...
That is why I'm confuse if I have a Deadlock o a wait lock...
That
Andrés,
may be you can enable the general log, recreate the deadlock,
and attach the general log?
If I had to reason as InnoDB, what I see is two updates statements that
arrive and want to update the same record,
I would be confused exactly as InnoDB is because I would not know which
update is
The genral log is the log that logs everything?
humm... dunno if I can.. as always... stuuupid production server with no
testing instance available...
And it happens very seldom, but force us to do a
select (sum) from the movements table instead just a select balance from
account...
On
Andres,
On Fri, May 11, 2012 at 1:48 PM, Andrés Tello mr.crip...@gmail.com wrote:
Ok, so I had a deadlock...
But then, why a deadlock doesn't rollback all the transaccion?
Because it can be resolved by rolling back just one of them. Why
destroy ALL the work people are trying to accomplish, if
humm, I see.. and if is encapusulated with it's own begin-commit inside a
bigger transacion, only that small part get rolled back...
If I get this straigth...
On Fri, May 11, 2012 at 2:32 PM, Baron Schwartz ba...@xaprb.com wrote:
Andres,
On Fri, May 11, 2012 at 1:48 PM, Andrés Tello
19 matches
Mail list logo
