BaoForPostgreSQL icon indicating copy to clipboard operation
BaoForPostgreSQL copied to clipboard

Workload running stuck when USE_BAO = False

Open LumingSun opened this issue 4 years ago • 4 comments

After I collected bao_run.txt and set USE_BAO = False to collect PG running behavior, I got stuck after running the 0 16query, and I compared with the bao_run, the next query is q1_8a463.sql. I tried several times and the process has no progress even after 9 hours. htop shows there are parallel PG worker running. It is very strange and I don't know why the run_queries.py is stuck.

LumingSun avatar Nov 19 '21 02:11 LumingSun

https://github.com/learnedsystems/BaoForPostgreSQL/blob/28142c74903cbf0873b614b3b4f3bc49c5f84a1f/run_queries.py#L34 Why use while True and continue here?

LumingSun avatar Nov 19 '21 03:11 LumingSun

same here; run_quries.py stuck at q1_8a463sql, in my pg log it says ERROR: canceling statement due to statement timeout. Have you got any solution for this issue?

ScottLiao920 avatar Jun 01 '22 11:06 ScottLiao920

@ScottLiao920 I just deleted continue in https://github.com/learnedsystems/BaoForPostgreSQL/blob/28142c74903cbf0873b614b3b4f3bc49c5f84a1f/run_queries.py#L34

LumingSun avatar Jun 01 '22 11:06 LumingSun

Based on my understanding, if you delete continue in https://github.com/learnedsystems/BaoForPostgreSQL/blob/28142c74903cbf0873b614b3b4f3bc49c5f84a1f/run_queries.py#L34 this query will be ignored after one failed attempt (in this case, timeout after 5 mins). If you want to run q1_8a463.sql, you may change the timeout setting here at https://github.com/learnedsystems/BaoForPostgreSQL/blob/28142c74903cbf0873b614b3b4f3bc49c5f84a1f/run_queries.py#L27 to 0, which means no timeout for upcoming queries.

ScottLiao920 avatar Jun 03 '22 08:06 ScottLiao920