Skip to content

Put errors on warning level for cpu set snapshots#18356

Merged
cryptoe merged 1 commit intoapache:masterfrom
uds5501:set_execeptions_to_warnings
Aug 5, 2025
Merged

Put errors on warning level for cpu set snapshots#18356
cryptoe merged 1 commit intoapache:masterfrom
uds5501:set_execeptions_to_warnings

Conversation

@uds5501
Copy link
Copy Markdown
Contributor

@uds5501 uds5501 commented Aug 4, 2025

Sending appropriate warnings when cpuset metrics are not available

}
catch (RuntimeException | IOException ex) {
LOG.error(ex, "Unable to read %s", file);
LOG.noStackTrace().warn(ex, "Unable to read %s, these metrics will be skipped", file);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: IMHO, it might be better to add all the CPUS_FILE, EFFECTIVE_CPUS_FILE etc in an array and then replace these with the exact metric name. That would help admins to figure out what happens with CPUS_FILE since the cluster admin would most likely grep for the particular string.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cryptoe , The file name will be mentioned here in the log already, just in separate log lines.

@cryptoe cryptoe merged commit 480fdc8 into apache:master Aug 5, 2025
72 checks passed
@cecemei cecemei added this to the 35.0.0 milestone Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants