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

can't get trino.execution.executor:name=TaskExecutor.RunningSplits #23078

Closed
wwbbcjeyc opened this issue Aug 20, 2024 · 3 comments
Closed

can't get trino.execution.executor:name=TaskExecutor.RunningSplits #23078

wwbbcjeyc opened this issue Aug 20, 2024 · 3 comments

Comments

@wwbbcjeyc
Copy link

wwbbcjeyc commented Aug 20, 2024

Introduce:
After upgrading to the v450 can't get trino.execution.executor:name=TaskExecutor.RunningSplits from http://worker:9300/v1/jmx/mbean .
Experimental config. experimental.thread-per-driver-scheduler-enabled was enabled by default since v438.When I disabled it, then this issue was removed..! 。

Problem:
There is no way to solve this problem without closing this configuration. Is there a new jmx that can be replaced

Tasks

Preview Give feedback
No tasks being tracked yet.
@wwbbcjeyc wwbbcjeyc changed the title Trino403 JMX for less than TaskExecutor. After upgrading to Trino450 RunningSplits indicators. Trino403 after upgrading to Trino450 JMX lost some indexes, such as: TaskExecutor. RunningSplits Aug 20, 2024
@wwbbcjeyc wwbbcjeyc changed the title Trino403 after upgrading to Trino450 JMX lost some indexes, such as: TaskExecutor. RunningSplits can't get trino.execution.executor:name=TaskExecutor.RunningSplits Aug 22, 2024
@sgoncharov1
Copy link

Hi, we experience the same issue.
We want to stay on default configuration, but as a result of this missing metrics ...

@wwbbcjeyc
Copy link
Author

您好,我们遇到了同样的问题。 我们想保留默认配置,但由于缺少指标...

I found a fix for this issue in the new version. The jmx mbean TaskExecutor was indeed deleted. The new metrics are provided below
#22914

@raunaqmorarka
Copy link
Member

Fixed by #22914

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants