trino.jvm.process_cpu_load
Process CPU utilizationDimensions:None
Available on:Native (1)
Interface Metrics (1)
Native
Recent CPU usage for the Trino JVM processDimensions:None
Technical Annotations (41)
Configuration Parameters (11)
query.remote-task.max-error-durationrecommended: 1mretry-policyrecommended: QUERYquery-retry-attemptsrecommended: 2-Xmx110Grecommended: 110G-XX:ReservedCodeCacheSizerecommended: 2G-XX:PerMethodRecompilationCutoffrecommended: 10000-XX:PerBytecodeRecompilationCutoffrecommended: 10000task.max-worker-threadsrecommended: lower than CPU counttask.concurrencytask.min-driverstask.info-update-intervalrecommended: 3sError Signatures (11)
io.trino.operator.PageTransportTimeoutExceptionexceptionjava.util.concurrent.TimeoutException: Total timeout 10000 ms elapsedexceptionio.trino.server.IoExceptionSuppressingWriterInterceptor Could not write to output: EofException(null)log patternSERVICE_UNAVAILABLEhttp statusio.trino.server.remotetask.SimpleHttpResponseHandler$ServiceUnavailableException: Server returned SERVICE_UNAVAILABLEexceptionMemory info update request to http://.*v1/memory has not returnedlog patternNode state update request to http://.*v1/info/state has not returnedlog patternError getting info for tasklog patternServer refused connectionlog patternFailed communicating with serverlog patternQUERY_CANCELEDerror codeCLI Commands (3)
top -H -p <pid>diagnosticjstack -l <pid>diagnosticEXPLAIN ANALYZE VERBOSEdiagnosticTechnical References (16)
Metabase v0.51.12componentStarburst Metabase driver v5.0componentTrino v457componentHttpPageBufferClientcomponent/v1/task/{task-id}/resultscomponentio.trino.$gen.PageFiltercomponentC2 CompilerThreadcomponentAzul Zulu JDK 17.0.4componenttask.max-worker-threadscomponentcoordinator-worker communicationconcept/v1/memoryfile path/v1/info/statefile path/v1/taskfile pathcoordinatorcomponentTaskInfoFetchercomponentRequestErrorTrackercomponentRelated Insights (11)
Cluster intermittently enters idle state after initial query executioncritical
▸
PageTransportTimeoutException occurs without worker failure or obvious resource exhaustionwarning
▸
Single worker CPU saturation causes cluster-wide query timeoutscritical
▸
C2 JIT compiler continuously recompiles PageFilter classeswarning
▸
Worker thread oversubscription starves coordinator-worker communication causing 503 errorscritical
▸
Coordinator bottleneck from hundreds of concurrent analystswarning
▸
Coordinator CPU exhausted polling dead tasks from terminated queriescritical
▸
Task concurrency misconfiguration causes performance degradationwarning
▸
Underutilized worker resources from low task.min-drivers settinginfo
▸
Suboptimal split scheduling from stale task informationinfo
▸
Queries canceled due to memory or CPU limit exceededwarning
▸