Implement statistic for iproto streams and remove in from `errinj` #6293

EvgenyMekhanik · 2021-08-05T13:21:48Z

At this moment, statistics on the number of streams and messages in streams are collected only for test purposes and stored in errinj to check that there is no memory leak in streams. Discuss what statistics are needed for streams, add it and remove statistics for streams from errinj.
Also at this moment we use errinj to collect iproto statistic per thread for test purpose. We store in errinj thread
number, which determine for what thread we want to get statistic. May be in this issue discuss and resolve it in other way.

The text was updated successfully, but these errors were encountered:

unera · 2021-08-24T12:09:49Z

Let's add the key STREAMS into box.stat.net:

STREAMS:
   active: 12
   requests:
        total: 123
        rps: 2    # last 5 second
   
   threads:
   - active: 12  # count of active streams
     requests:
        total: 123
        rps: 2    # last 5 second
   - active: 0
     requests:
         total: 0
         rps: 0

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. Part of #6293

…at.net` Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps and total and threads. For example: STREAMS: current: 0 rps: 17980 totat: 112623 threads: total: 0 rps: 0 total: 112623 rps: 17980

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now getting network statistic per thread was implemented. For example if user run three iproto threads `SEND` metric for network statistic: SENT: threads: - total: 0 rps: 0 - total: 0 rps: 0 - total: 48452 rps: 5795 rps: 5795 total: 48452 `threads` metric was added, it contains statistics per thread.

…at.net` Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps, total and threads. For example: STREAMS: current: 0 rps: 17980 totat: 112623 threads: total: 0 rps: 0 total: 112623 rps: 17980

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now getting network statistic per thread was implemented. For example if user run three iproto threads `SEND` metric for network statistic: SENT: threads: - total: 0 rps: 0 - total: 0 rps: 0 - total: 48452 rps: 5795 rps: 5795 total: 48452 `threads` metric was added, it contains statistics per thread.

…at.net` Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps, total and threads. For example: STREAMS: current: 0 rps: 17980 totat: 112623 threads: total: 0 rps: 0 total: 112623 rps: 17980

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now getting network statistic per thread was implemented. For example if user run three iproto threads `SEND` metric for network statistic: SENT: threads: - total: 0 rps: 0 - total: 0 rps: 0 - total: 48452 rps: 5795 rps: 5795 total: 48452 `threads` metric was added, it contains statistics per thread.

…at.net` Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps, total and threads. For example: STREAMS: current: 0 rps: 17980 totat: 112623 threads: total: 0 rps: 0 total: 112623 rps: 17980

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. In this patch `box.stat.net.thread` was implemented, it can be used for getting same statistics as from `box.stat.net` but per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now `box.stat.net.thread` was implemented for getting same statistics as when using `box.stat.net` but per thread. User can called it as a function `box.stat.net.thread()` for getting common network statistic per thread. For example for two iproto threads: --- - - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ... Also user can indexed it as a table by thread number. For example `box.stat.net.thread[1]` returns network statistic for first iproto thread: --- - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ...

Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps and total. For example: STREAMS: current: 0 rps: 17980 totat: 112623

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. In this patch `box.stat.net.thread` was implemented, it can be used for getting same statistics as from `box.stat.net` but per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now `box.stat.net.thread` was implemented for getting same statistics as when using `box.stat.net` but per thread. User can called it as a function `box.stat.net.thread()` for getting common network statistic per thread. For example for two iproto threads: --- - - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ... Also user can indexed it as a table by thread number. For example `box.stat.net.thread[1]` returns network statistic for first iproto thread: --- - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ...

Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as other metrics in `box.stat.net`: current, rps and total. For example: STREAMS: current: 0 rps: 17980 totat: 112623

Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as `CONNECTIONS` metric in `box.stat.net`: current, rps and total. For example: STREAMS: current: 0 rps: 17980 totat: 112623

@TarantoolBot

Currently getting iproto statistics per thread is possible only in debug mode, using `ERRINJ_IPROTO_SINGLE_THREAD_STAT` (it can be used only in tests). This way have several disadvantages: first of all `errinj` is not a place to get statistics, secondly user may be interested in getting iproto statistics per thread. In this patch `box.stat.net.thread` was implemented, it can be used for getting same statistics as from `box.stat.net` but per thread. Part of #6293 @TarantoolBot document Title: getting network statistic per thread was implemented User has possibility to run several iproto threads, but at the moment he can get only general statistics, which combines statistics for all threads. Now `box.stat.net.thread` was implemented for getting same statistics as when using `box.stat.net` but per thread. User can called it as a function `box.stat.net.thread()` for getting common network statistic per thread. For example for two iproto threads: --- - - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ... Also user can indexed it as a table by thread number. For example `box.stat.net.thread[1]` returns network statistic for first iproto thread: --- - SENT: total: 0 rps: 0 CONNECTIONS: current: 0 rps: 0 total: 0 REQUESTS: current: 0 rps: 0 total: 0 RECEIVED: total: 0 rps: 0 ...

Currently there are several statistic metrics for iproto, which can be obtained by using `box.stat.net`: `CONNECTIONS`, `REQUESTS`, `SENT` and `RECEIVED`. Add new metric `STREAMS` which contain statistics for iproto streams. Closes #6293 Title: getting statistics for iproto streams was implemented Add new metric `STREAMS` to `box.stat.net`, which contain statistics for iproto streams. `STREAMS` contains same counters as `CONNECTIONS` metric in `box.stat.net`: current, rps and total. For example: STREAMS: current: 0 rps: 17980 totat: 112623

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). Closes #6293 @TarantoolBot document Title: getting statistics for queues of iproto streams was implemented Add new metric `STREAM_QUEUE_MAX` to `box.stat.net`. This metric contains two counters `current` (displays the current length of the longest stream queue) and `total` (displays the maximal length of the stream queue for all time). ``` STREAM_QUEUE_MAX current: -- current length of the longest stream queue total: -- maximal length of the stream queue for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

@TarantoolBot

Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. Part of #6293 @TarantoolBot document Title: detailed iproto requests statistics was implemented Add new metrics `REQUESTS_IN_PROGRESS` and `REQUESTS_IN_STREAM_QUEUE` to `box.stat.net`, which contain detailed statistics for iproto requests. These metrics contains same counters as other metrics in `box.stat.net`: current, rps and total. ``` -- statistics for requests currently being processed in tx thread. REQUESTS_IN_PROGRESS: current: -- count of requests currently being processed in the tx thread rps: -- count of requests processed by the tx thread per second total: -- total count of requests processed by tx thread -- statistics for requests placed in queues of streams. REQUESTS_IN_STREAM_QUEUE: current: -- count of requests currently waiting in queues of streams rps: -- count of requests placed in streams queues per second total: -- total count of requests, which was placed in queues of streams for all time ```

The test checks that the number of IPROTO requests handled by a test server is reported correctly in statistics. Since a net.box connection sends a few "service" requests (e.g. to fetch schema), the test excludes them from the total count. The problem is this doesn't always work with service requests sent to enable graceful shutdown. To enable graceful shutdown a client sends an IPROTO_WATCH request. The server replies to the client with IPROTO_EVENT. Upon receiving the event, the client sends another IPROTO_WATCH request to ack it. The whole procedure is fully asynchronous, which means it may finish after we start processing user requests over the connection. To correctly account service requests, let's disable this feature. Closes tarantool/tarantool-qa#269 NO_DOC=test fix NO_CHANGELOG=test fix

The test checks that the number of IPROTO requests handled by a test server is reported correctly in statistics. Since a net.box connection sends a few "service" requests (e.g. to fetch schema), the test excludes them from the total count. The problem is this doesn't always work with service requests sent to enable graceful shutdown. To enable graceful shutdown a client sends an IPROTO_WATCH request. The server replies to the client with IPROTO_EVENT. Upon receiving the event, the client sends another IPROTO_WATCH request to ack it. The whole procedure is fully asynchronous, which means it may finish after we start processing user requests over the connection. To correctly account service requests, let's disable this feature. Closes tarantool/tarantool-qa#269 NO_DOC=test fix NO_CHANGELOG=test fix (cherry picked from commit 4e9bffc)

EvgenyMekhanik added feature A new functionality incoming labels Aug 5, 2021

EvgenyMekhanik self-assigned this Aug 5, 2021

kyukhin added teamC and removed incoming labels Aug 13, 2021

alyapunov added the 3sp label Aug 13, 2021

kyukhin added this to the 2.10.1 milestone Aug 19, 2021

kyukhin added the in design Requires design document label Aug 20, 2021

unera removed the in design Requires design document label Aug 25, 2021

patiencedaur mentioned this issue Jan 20, 2022

[Epic] iproto streams follow-ups tarantool/doc#2589

Closed

12 tasks

coveralls mentioned this issue Mar 13, 2023

test: fix flaky box/gh-6293-implement-new-net-stat #8430

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Implement statistic for iproto streams and remove in from `errinj` #6293

Implement statistic for iproto streams and remove in from `errinj` #6293

EvgenyMekhanik commented Aug 5, 2021

unera commented Aug 24, 2021 •

edited

Loading

Implement statistic for iproto streams and remove in from errinj #6293

Implement statistic for iproto streams and remove in from errinj #6293

Comments

EvgenyMekhanik commented Aug 5, 2021

unera commented Aug 24, 2021 • edited Loading

Implement statistic for iproto streams and remove in from `errinj` #6293

Implement statistic for iproto streams and remove in from `errinj` #6293

unera commented Aug 24, 2021 •

edited

Loading