farovictor commented on issue #33252:
URL: https://github.com/apache/superset/issues/33252#issuecomment-2940608634

   > [@farovictor](https://github.com/farovictor) Did You manage to solve your 
problem with more proper way than workaround you mentioned? Were You able to 
find out what other process is trying to access that `dashboard_roles` table 
causing deadlock?
   > 
   > I have similar problem (exactly the same log except process ids), during 
the same migration file processing: 
`2023-09-15_12-58_4b85906e5b91_add_on_delete_cascade_for_dashboard_roles.py`. I 
encounter it only on AWS environment with Aurora PostgreSQL and all my tries to 
reproduce it on different environment using normal PostgreSQL failed (though, I 
have no idea what are the differenties between this one and Aurora PostgreSQL 
and whether they exists at all). I do not do any real migration there, anyway. 
It's just superset-init-db execution on fresh, empty environment. It fails 
every time on AWS with Aurora and I ran out of ideas what might be causing this.
   > 
   > I use helm chart 0.13.1 with docker image based on 4.0.2 version of 
Superset with Python 3.10 inside. The error seems to be occurring during 
execution of `superset db upgrade` command in initscript.
   > 
   > Now, I wonder if it can be caused by migration file 
`2023-09-06_13-18_317970b4400c_added_time_secondary_column_to_.py` being 
alphabetically directly before the problematic migration file mentioned earlier 
which is the only file with execution privileges. As I said, I ran out of 
ideas...
   
   Sadly, no!
   
   I had to manually set deployments to 0 replicas to make jobs pass.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to