You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The content you are editing has changed. Please copy your edits and refresh the page.
The text was updated successfully, but these errors were encountered:
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
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
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
The text was updated successfully, but these errors were encountered: