You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, `TestDistSQLReceiverReportsContention` with
`contention=false` test case asserted that no contention has been
observed since we reset the state. However, we have sources of
contention among internal queries (in some test runs I observed
contention on `system.jobs`, `system.job_info`, and
`system.scheduled_jobs` tables), so we previously tried to eliminate
reporting of that via disabling the txn stats sampling, yet we still see
this test fail occasionally. In order for a contention event to be
reported, we only need to have Structured recording level enabled in the
trace. On a quick glance I didn't find where that happens (e.g. we
recently added `sql.trace.txn.sample_rate` cluster setting which is another
way to enable things, but disabling it didn't fix the flake), and
I don't think it's actually worth figuring this out for this test. The
main goal of the test is ensuring that we do and don't have contention
on _our_ table, so this commit relaxes the test a bit. In
`contention=false` test case we now only check that our table isn't
present in the contention registry.
Release note: None
0 commit comments