MySQL can deadlock on garbage collection
See original GitHub issue...
/silk/models.py", line 167, in save
Request.garbage_collect(force=False)
/silk/models.py", line 152, in garbage_collect
cls.objects.filter(start_time__lte=time_cutoff).delete()
...
/silk/sql.py", line 45, in execute_sql
return self._execute_sql(*args, **kwargs)
...
django.db.utils.OperationalError: (1213, 'Deadlock found when trying to get lock; try restarting transaction')
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:10 (2 by maintainers)
Top Results From Across the Web
MySQL Bugs: #59733: Possible deadlock when buffered ...
When a table is dropped and re-created with innodb_file_per_table=1, the insert buffer bitmap pages for the old space_id will be dropped, and ...
Read more >Mysql/JDBC: Deadlock - java - Stack Overflow
Solved: I wrongly declared a ResultSet as updateable. The ResultSet was closed only on a "finalize()" method via Garbage Collector which was not...
Read more >Deadlocked! - Coding Horror
This sets the transaction isolation level to read uncommitted , also known as "dirty reads". It tells the query to use the lowest...
Read more >Deadlocks and database connection issues 7.8.3 version
“pause-the-world”. 6.3 seconds. That kind of garbage collector pause breaks lots of things in Ignition. You might have other problems (since you ...
Read more >Php – How to retry transaction after a deadlock using Doctrine ...
databasedeadlockdoctrine-ormmysqlphp ... Well, you could simply adjust these values so that the garbage collector is started more often.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same issue with PostgreSQL 10.6 and Django 2.2
I don’t see why this doesn’t get more attention. In my opinion this is a serious issue which prevents us from using Silk. Are there any workarounds I am missing?