[MXS-3240] Uom variable from maxscale api /maxscale/threads Created: 2020-10-15  Updated: 2020-10-19  Resolved: 2020-10-19

Status: Closed
Project: MariaDB MaxScale
Component/s: Documentation
Affects Version/s: 2.4.12
Fix Version/s: 2.4.14

Type: Bug Priority: Major
Reporter: febriyant Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: api, maxscale
Environment:

CentOS 7


 Description   

hi i already got data from maxscale api from this url /maxscale/threads.
but i don know about data type from this key.

"stats": {
 
                    "reads": 61192121, /*this is byte ? */
 
                    "writes": 61769861,  /*this is byte ? */
 
                    "errors": 107212, /*this is byte ? */
 
                    "hangups": 167974, /*this is byte ? */
 
                    "accepts": 138529, /*this is byte ? */
 
                    "avg_event_queue_length": 1,
 
                    "max_event_queue_length": 72,
 
                    "max_exec_time": 9, /*this is seconds or miliseconds */
 
                    "max_queue_time": 5,/*this is seconds or miliseconds */
 
                    "current_descriptors": 489,
 
                    "total_descriptors": 415040,
 
                    "load": {
 
                        "last_second": 1,
 
                        "last_minute": 1,
 
                        "last_hour": 1
 
                    },
 
                    "query_classifier_cache": {
 
                        "size": 12604105, /*this is byte ? */
 
                        "inserts": 13124, /*this is byte ? */
 
                        "hits": 21161618, /*this is byte ? */
 
                        "misses": 13124, /*this is byte ? */
 
                        "evictions": 0
 
                    }



 Comments   
Comment by markus makela [ 2020-10-15 ]

The reads, writes, errors, hangups and accepts are all counts of how many of those events the thread has processed. The size in query_classifier_cache is in bytes. The other ones are counts of how many of these events have occurred.

The max_exec_time and max_queue_time are currently measured as number of internal ticks (100ms per tick). These should be converted to milliseconds so that there's no need to convert it on the client side.

Comment by febriyant [ 2020-10-16 ]

thanks for update

for this key this is same with max_exec_time ?

"avg_event_queue_length": 1,
 
"max_event_queue_length": 72,

Comment by markus makela [ 2020-10-16 ]

avg_event_queue_length is the average number of epoll events returned in a single call. max_event_queue_length is the maximum for this.

Comment by febriyant [ 2020-10-16 ]

ok thanks

Generated at Thu Feb 08 04:19:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.