I get no results from running that query. lockable_object_type = 'relation ' AND t. starttime > ( current_timestamp - interval '2 minutes ')ĪND q.
#REDSHIFT ALTER TABLE HANGS HOW TO#
"os.version": "4.14.86_64",Īs for the 6 points, are you referring to the list beginning with "What is the time zone of the data you think is being displayed improperly?"? I'm not having issues with timezones or wrong numbers, so this doesn't seem relevant / I don't know how to answer these. "java.vm.name": "OpenJDK 64-Bit Server VM", T16:52:26-08:00 INFO Query took 2266 ms to run miminum for cache eligibility is 15000 ms T16:52:26-08:00 WARN -userland-query Query failure When the deadlocks occur, it starts to block most queries and dashboards that normal users at our company need. We're experiencing deadlocks around once every day or every other day, which is preventing our company from relying on Metabase for data analysis.
If applicable, add screenshots to help explain your problem. My expectation would be that Metabase always releases any locks that it acquires in the process of running a query once that query is complete. Any ideas? Has anybody experienced a similar issue using Metabase with Redshift and other processes that occasionally change/update the underlying tables? I can't figure out how Metabase would be running a query that results in an perpetually open transaction holding locks. Pid | starttime | endtime | aborted | querystart Redshift=# select pid, starttime, endtime, aborted, substring (querytxt,1,40) as querystart from stl_query where pid = 30037 Looking at the logged info about the query for that pid, we see that it was a Metabase query that took just over a minute to run and was not aborted.
(Other similar transactions for different PIDs opened by Metabase) Txn_owner | txn_db | pid | txn_start | lock_mode | lockable_object_type | table | granted Redshift=# select txn_owner,txn_db,pid,txn_start,lock_mode,lockable_object_type,svv_table_info.table,granted from svv_transaĬtions left join svv_table_info on svv_transactions.relation = svv_table_info.table_id where pid pg_backend_pid() order b
0 kommentar(er)
