roachtest: run EXPLAIN ANALYZE (DEBUG) in tpchvec/perf on failure #50253
Conversation
In order to get more information that could explain occasional slowness on query 7 this commit updates the usage of `EXPLAIN ANALYZE` to `EXPLAIN ANALYZE (DEBUG)` which will provide us with traces and other useful information. The bundles are `curl`ed into `logs` folder so that the test runner fetched it alongside normal log files. Release note: None
|
This change is |
There was a problem hiding this comment.
Nice. Is EXPLAIN ANALYZE (DEBUG) available on all versions this test runs against?
Reviewed 1 of 1 files at r1.
Reviewable status:complete! 1 of 0 LGTMs obtained
There was a problem hiding this comment.
Nice. Is
EXPLAIN ANALYZE (DEBUG)available on all versions this test runs against?
I didn't think about this initially, but the command is present on 20.1 version and onwards. tpchvec/perf also runs on 19.2 version, but we haven't had a single random slow failure on 19.2 since we increased the slowness threshold to 1.5 like 3 months ago, so I think it should be ok to use this command. I see it as a temporary measure to try to understand the intermittent slowness on query 7 and intend on removing it once we figure that out.
TFTR!
bors r+
Reviewable status:
Build succeeded |
In order to get more information that could explain occasional slowness
on query 7 this commit updates the usage of
EXPLAIN ANALYZEtoEXPLAIN ANALYZE (DEBUG)which will provide us with traces and otheruseful information. The bundles are
curled intologsfolder so thatthe test runner fetched it alongside normal log files.
Addresses: #50029.
Release note: None