Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip non-existent MBeans in JmxRecordSetProvider #24908

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

piotrrzysko
Copy link
Member

@piotrrzysko piotrrzysko commented Feb 5, 2025

Description

When dynamic catalogs are enabled, and multiple catalogs use the same connector, querying a metric associated with the connector may return results only from the coordinator if not all catalogs have been used yet. This happens because the corresponding MBeans haven't been registered on the workers.

With this change, the query will return results from workers for catalogs that have already been used and whose MBeans have been registered, while gracefully skipping non-existent MBeans.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## Section
* Fix querying non-existent JMX metrics. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Feb 5, 2025
When dynamic catalogs are enabled, and multiple catalogs use the same
connector, querying a metric associated with the connector may return
results only from the coordinator if not all catalogs have been used
yet. This happens because the corresponding MBeans haven't been
registered on the workers.

With this change, the query will return results from workers for
catalogs that have already been used and whose MBeans have been
registered, while gracefully skipping non-existent MBeans.
@wendigo wendigo merged commit e78c06b into trinodb:master Feb 5, 2025
51 checks passed
@github-actions github-actions bot added this to the 470 milestone Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants