...
HiveMQ uses task queues to manage and execute asynchronous tasks efficiently. It receives incoming work, splits it into tasks and adds them to a queue which is processed one by one in a controlled and orderly manner. Each task is typically a discrete unit of work and can be executed independently.
The tasks can be grouped into the following 4 categories:
Persistence tasks
These tasks relate to disk reads and writes.
Total tasks
| Code Block |
|---|
com.hivemq.persistence-executor.queued com.hivemq.persistence.executor.total.tasks |
Connection establishment tasks
| Code Block |
|---|
com.hivemq.persistence_executor.client-events.tasks com.hivemq.persistence_executor.client-session.tasks |
Messaging tasks
| Code Block |
|---|
com.hivemq.persistence_executor.incoming-message-flow.tasks com.hivemq.persistence_executor.queued.messages.tasks |
Single-writer-callback tasks
These tasks relate to data replication between individual cluster members
com.hivemq.single-writer-callback-executor.*.queued
Netty tasks
These tasks are related to Network Input-Output throughput
Extension tasks
These tasks denote SDK calls made by extensions
com.hivemq.extension.task.executors.queued
How to query these metrics?
| Expand | ||
|---|---|---|
| ||
|
...