| 2015-01-20 09:11:28 |
Peiran Song |
description |
From a customer's SHOW ENGINE INNODB STATUS samples, we found one transaction first in ROLLING BACK and then continued on. I never encountered this before and don't know how to reproduce it. But the customer sees ROLLING BACK in the transaction section for this query from time to time.
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec inserting
mysql tables in use 1, locked 1
ROLLING BACK 461 lock struct(s), heap size 63928, 1435 row lock(s), undo log entries 1217
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, is_delivered, is_bounced, is_soft_bounced, is_opened, is_clicked, is_unsubscribed, first_sent_datehour, first_sent_at, last_activity_at, created_at, updated_at) VALUES (1339,1136,8124716,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:51','15-01-11 05:38:51',NOW(),NOW()),(1742,1629,27909032,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:38','15-01-11 05:38:38',NOW(),NOW()),(1743,1644,4968364,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 0
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec starting index read
mysql tables in use 1, locked 1
489 lock struct(s), heap size 80312, 1463 row lock(s), undo log entries 1231
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, |
From a customer's SHOW ENGINE INNODB STATUS samples, we found one transaction first in ROLLING BACK and then continued on. I never encountered this before and don't know how to reproduce it. But the customer sees ROLLING BACK in the transaction section for this query from time to time.
Server version: PS 5.5.28
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec inserting
mysql tables in use 1, locked 1
ROLLING BACK 461 lock struct(s), heap size 63928, 1435 row lock(s), undo log entries 1217
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, is_delivered, is_bounced, is_soft_bounced, is_opened, is_clicked, is_unsubscribed, first_sent_datehour, first_sent_at, last_activity_at, created_at, updated_at) VALUES (1339,1136,8124716,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:51','15-01-11 05:38:51',NOW(),NOW()),(1742,1629,27909032,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:38','15-01-11 05:38:38',NOW(),NOW()),(1743,1644,4968364,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 0
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec starting index read
mysql tables in use 1, locked 1
489 lock struct(s), heap size 80312, 1463 row lock(s), undo log entries 1231
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, |
|
| 2015-01-20 09:51:57 |
Peiran Song |
description |
From a customer's SHOW ENGINE INNODB STATUS samples, we found one transaction first in ROLLING BACK and then continued on. I never encountered this before and don't know how to reproduce it. But the customer sees ROLLING BACK in the transaction section for this query from time to time.
Server version: PS 5.5.28
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec inserting
mysql tables in use 1, locked 1
ROLLING BACK 461 lock struct(s), heap size 63928, 1435 row lock(s), undo log entries 1217
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, is_delivered, is_bounced, is_soft_bounced, is_opened, is_clicked, is_unsubscribed, first_sent_datehour, first_sent_at, last_activity_at, created_at, updated_at) VALUES (1339,1136,8124716,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:51','15-01-11 05:38:51',NOW(),NOW()),(1742,1629,27909032,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:38','15-01-11 05:38:38',NOW(),NOW()),(1743,1644,4968364,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 0
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec starting index read
mysql tables in use 1, locked 1
489 lock struct(s), heap size 80312, 1463 row lock(s), undo log entries 1231
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 ab04db1.marketo.org 10.1.13.82 tungsten update
INSERT INTO myfitnesspalBetacust.email_campaign_activity (mailing_def_id, smart_campaign_id, lead_person_id, rule_key_id, type, is_sent, |
From a customer's SHOW ENGINE INNODB STATUS samples, we found one transaction first in ROLLING BACK and then continued on. I never encountered this before and don't know how to reproduce it. But the customer sees ROLLING BACK in the transaction section for this query from time to time.
Server version: PS 5.5.28
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec inserting
mysql tables in use 1, locked 1
ROLLING BACK 461 lock struct(s), heap size 63928, 1435 row lock(s), undo log entries 1217
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 myserver 10.1.13.82 tungsten update
INSERT INTO mydb.mytable (c1, c2, c3, c4, c5, c6...) VALUES (1339,1136,8124716,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:51','15-01-11 05:38:51',NOW(),NOW()),(1742,1629,27909032,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 05:38:38','15-01-11 05:38:38',NOW(),NOW()),(1743,1644,4968364,0,'m',1,1,0,0,1,0,0,'15-01-11 05:00:00','15-01-11 0
17:07:10
---TRANSACTION 182AC2408, ACTIVE 8 sec starting index read
mysql tables in use 1, locked 1
489 lock struct(s), heap size 80312, 1463 row lock(s), undo log entries 1231
MySQL thread id 225564, OS thread handle 0x7f45dd7e2700, query id 1383215000 myserver 10.1.13.82 tungsten update
INSERT INTO mydb.mytable (c1, c2, c3, c4, c5, c6...) VALUES |
|
