Writing clickhouse timings to csv after each query does not works anymore.
Previously run version of clickhouse which worked fine was 20.3.8.53. It was run on 2020-06-20.
It seems that clickhouse got upgraded recently on production machine and current version is 20.9.3.45. This is most likely a reason why expected timings data has not been written properly to csv files.
I filled a ticket to understand why upgrade happened so we prevent these kind of issues in future.
When we do upgrade we need to ensure it is running properly after upgrade in a test workflow, not a production workflow, because as of now, it will produce db-benchmark report showing clickhouse having "undefined exception" for all queries.
jangorecki
commented
3 years ago
Writing clickhouse timings to csv after each query does not works anymore. Previously run version of clickhouse which worked fine was 20.3.8.53. It was run on 2020-06-20. It seems that clickhouse got upgraded recently on production machine and current version is 20.9.3.45. This is most likely a reason why expected timings data has not been written properly to csv files. I filled a ticket to understand why upgrade happened so we prevent these kind of issues in future. When we do upgrade we need to ensure it is running properly after upgrade in a test workflow, not a production workflow, because as of now, it will produce db-benchmark report showing clickhouse having "undefined exception" for all queries.