cockroachdb / cockroachdb/cockroach
server,sql: investigate if statsRefresher should be started later
Open
A-server-start-drain
A-sql-table-stats
C-investigation
T-sql-queries
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Currently the statsRefresher service -- which triggers stats refresh jobs -- is started in preStart relatively early, indeed before the job service that could run those jobs is started, before various other services, and perhaps more interestingly before version upgrades are run or the minimum version compatibility for secondary tenants is checked. Should it start later? And are there any other sql background services that should be started later?
Jira issue: CRDB-24438
Contributor guide
Assessment
This issue has not been assessed yet.