-
Notifications
You must be signed in to change notification settings - Fork 4.1k
schedulinglogging: some cluster setting values cause CPU usage to increase to 100% #87771
Copy link
Copy link
Closed
Labels
A-loggingIn and around the logging infrastructure.In and around the logging infrastructure.A-sql-logging-and-telemetryIssues related to slow query log, SQL audit log, SQL internal logging telemetry, etc.Issues 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.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Description
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-loggingIn and around the logging infrastructure.In and around the logging infrastructure.A-sql-logging-and-telemetryIssues related to slow query log, SQL audit log, SQL internal logging telemetry, etc.Issues 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.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.