Skip to content

schedulinglogging: some cluster setting values cause CPU usage to increase to 100% #87771

@knz

Description

@knz

Describe the problem

If I set the following cluster settings:

set cluster setting "sql.telemetry.capture_index_usage_stats.interval" = '0s';
set cluster setting "sql.telemetry.capture_index_usage_stats.check_enabled_interval" = '0s';
set cluster setting "sql.telemetry.capture_index_usage_stats.logging_delay" = '0s';

Then the task "capture-index-usage-stats" starts to busy-loop with a zero timer.

Expected behavior

There should be a minimum delay between iterations to avoid a busy loop.

Jira issue: CRDB-19524

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-loggingIn and around the logging infrastructure.A-sql-logging-and-telemetryIssues related to slow query log, SQL audit log, SQL internal logging telemetry, etc.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions