Most jobs in CockroachDB set up a DistSQL flow that describes their execution. This flow may be planned and re-planned several times during the lifetime of a job if its execution is restarted due to transient errors. SQL queries already have a way of generating and displaying a schematic diagram of this flow. This diagram is helpful to understand the distribution of work across the cluster. With the introduction of the job_info table, each job now has the ability to persist information about its execution. This issue tracks the work to generate, and persist the DistSQL diagram for an executing job. As noted above a single job may have many such entries which will also be useful to see how the execution plan changes over time.
Jira issue: CRDB-26043
Epic: CRDB-8964
Most jobs in CockroachDB set up a DistSQL flow that describes their execution. This flow may be planned and re-planned several times during the lifetime of a job if its execution is restarted due to transient errors. SQL queries already have a way of generating and displaying a schematic diagram of this flow. This diagram is helpful to understand the distribution of work across the cluster. With the introduction of the
job_infotable, each job now has the ability to persist information about its execution. This issue tracks the work to generate, and persist the DistSQL diagram for an executing job. As noted above a single job may have many such entries which will also be useful to see how the execution plan changes over time.Jira issue: CRDB-26043
Epic: CRDB-8964