Describe the problem

In v24.3.14, the sql.stats.automatic_job_check_before_creating_job.enabled settings was introduced. This setting reduces the level of stats-induced contention on the jobs table by performing the check to see if a stats job already exists outside of the transaction that creates the stats job. While this does reduce contention, it opens up the possibility that multiple nodes will simultaneously try to create stats jobs, resulting in one or more of them failing.

In v24.3.14, failing to create the stats job results in a warning in the server log. Alert customers may note this error and become alarmed that their mission critical cluster is degraded, when in fact this is a normal part of operation. We should not issue this failure notification as a warning.

Jira issue: CRDB-51606