Tjyylli

Where to find documentation for `whois` command options?

Simulate round-robin tournament draw

SQL Server placement of master database files vs resource database files

How would you suggest I follow up with coworkers about our deadline that's today?

What *exactly* is electrical current, voltage, and resistance?

What is /etc/mtab in Linux?

Why doesn't the university give past final exams' answers?

What is the purpose of the side handle on a hand ("eggbeater") drill?

What helicopter has the most rotor blades?

Is there a possibility to generate a list dynamically in Latex?

Why does Java have support for time zone offsets with seconds precision?

Will I be more secure with my own router behind my ISP's router?

Why aren't road bicycle wheels tiny?

What's called a person who works as someone who puts products on shelves in stores?

In search of the origins of term censor, I hit a dead end stuck with the greek term, to censor, λογοκρίνω

Is it appropriate to mention a relatable company blog post when you're asked about the company?

Is there a way to fake a method response using Mock or Stubs?

How was Lagrange appointed professor of mathematics so early?

Putting Ant-Man on house arrest

`FindRoot [ ]`::jsing: Encountered a singular Jacobian at a point...WHY

How long can a nation maintain a technological edge over the rest of the world?

How to translate "red flag" into Spanish?

Test if all elements of a Foldable are the same

What were wait-states, and why was it only an issue for PCs?

Deadlock error on mysql not in a transaction

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

0

I get this error:

[DoctrineDBALExceptionDeadlockException] An exception occurred
while executing ' UPDATE pipeline__message SET process_id = ?,
state = ?, updated_at = NOW() WHERE state = "available" AND topic
IN ('refresh_subscription') AND available_at <= NOW() ORDER BY
available_at ASC LIMIT 1' with params
["4c4d1768-65cd-11e9-a8ef-1224ebe6b80e", "processing"]:

SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock; try restarting transaction

I am not executing this query in a transaction and there is only one query so there is not "query order" problem.

This query is executed via a a daemon, multiple daemon are running at the same time, so the same query (with a diff unique process_id) can be executed at the "same" time.

Everything I read about deadlock are related to transaction "locking" the same row to be able to proceed which doesn't make sens in my current use case.

Engine is a AWS/Aurora/MySql 5.7.12

What could be the cause and how can I fix that ?

mysql

share|improve this question

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are there tiggers on the table? Are any other (unrelated) transactions running?
  
  – Eugen Rieck
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There is no trigger on any table. Not suppose to have any transaction on the daemon itself, may have other transaction on other process.
  
  – Martin Poirier Théorêt
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Make sure to retry without those other transactions - if they are long-runinng the might create a deadlock.
  
  – Eugen Rieck
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's is not what a deadlock is suppose to be base on my understanding. If I am not trying to have a lock (not in a transaction) how could I have a deadlock ?
  
  – Martin Poirier Théorêt
  8 hours ago
  

  
  
  
  

add a comment | 

0

I get this error:

[DoctrineDBALExceptionDeadlockException] An exception occurred
while executing ' UPDATE pipeline__message SET process_id = ?,
state = ?, updated_at = NOW() WHERE state = "available" AND topic
IN ('refresh_subscription') AND available_at <= NOW() ORDER BY
available_at ASC LIMIT 1' with params
["4c4d1768-65cd-11e9-a8ef-1224ebe6b80e", "processing"]:

SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock; try restarting transaction

I am not executing this query in a transaction and there is only one query so there is not "query order" problem.

This query is executed via a a daemon, multiple daemon are running at the same time, so the same query (with a diff unique process_id) can be executed at the "same" time.

Everything I read about deadlock are related to transaction "locking" the same row to be able to proceed which doesn't make sens in my current use case.

Engine is a AWS/Aurora/MySql 5.7.12

What could be the cause and how can I fix that ?

mysql

share|improve this question

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are there tiggers on the table? Are any other (unrelated) transactions running?
  
  – Eugen Rieck
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There is no trigger on any table. Not suppose to have any transaction on the daemon itself, may have other transaction on other process.
  
  – Martin Poirier Théorêt
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Make sure to retry without those other transactions - if they are long-runinng the might create a deadlock.
  
  – Eugen Rieck
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's is not what a deadlock is suppose to be base on my understanding. If I am not trying to have a lock (not in a transaction) how could I have a deadlock ?
  
  – Martin Poirier Théorêt
  8 hours ago
  

  
  
  
  

add a comment | 

I get this error:

[DoctrineDBALExceptionDeadlockException] An exception occurred
while executing ' UPDATE pipeline__message SET process_id = ?,
state = ?, updated_at = NOW() WHERE state = "available" AND topic
IN ('refresh_subscription') AND available_at <= NOW() ORDER BY
available_at ASC LIMIT 1' with params
["4c4d1768-65cd-11e9-a8ef-1224ebe6b80e", "processing"]:

SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock; try restarting transaction

I am not executing this query in a transaction and there is only one query so there is not "query order" problem.

This query is executed via a a daemon, multiple daemon are running at the same time, so the same query (with a diff unique process_id) can be executed at the "same" time.

Everything I read about deadlock are related to transaction "locking" the same row to be able to proceed which doesn't make sens in my current use case.

Engine is a AWS/Aurora/MySql 5.7.12

What could be the cause and how can I fix that ?

mysql

share|improve this question

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited 10 hours ago

Dave

22227

edited 10 hours ago

Dave

22227

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1

New contributor

Martin Poirier Théorêt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 11 hours ago

Martin Poirier ThéorêtMartin Poirier Théorêt

1