# 10min\_netisr\_backlog\_exceeded

**URL:** <https://community.netdata.cloud/t/10min-netisr-backlog-exceeded/1902>\
**Category:** Alerts\
**Created:** [November 3, 2021, 1:05pm UTC](https://community.netdata.cloud/t/10min-netisr-backlog-exceeded/1902 "2021-11-03T13:05:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tasos\_Katsoulas](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/tasos_katsoulas/32/1344_2.png) [@Tasos\_Katsoulas](https://community.netdata.cloud/u/Tasos_Katsoulas)\
**Post date:** [November 3, 2021, 1:05pm UTC](https://community.netdata.cloud/t/10min-netisr-backlog-exceeded/1902/1 "2021-11-03T13:05:04Z")

</div>

# 10min\_netisr\_backlog\_exceeded

## OS: FreeBSD

The netisr\_maxqlen is a queue within the network kernel dispatch service of FreeBSD kernel which keeps packets received by interfaces and not yet processed by destined subsystems or userland applications. The system drops new packets when the queue is full. There may be several netisr packet queues in the system and raising `netisr_maxqlen` allows all of them to grow. The default `netisr_maxqlen` value should be 256 in most of the FreeBSD versions. However this may not be enough in some cases, such as:

- Multiple interfaces operating at 1Gbps, or even a single interface at 10Gbps.

- Lower powered systems process very large amounts of network traffic.

Netdata agent monitors the average number of dropped packets in the last minute due to exceeded netisr queue length.

### Troubleshooting section:

> **Increase the netisr\_maxqlen value.**
>
> 1. Check your current value.
> 
> 2. Try to increase it by a factor of 4.
> 
> 3. Verify the change and test with the same workload that triggered the alarm originally.
> 
> 4. If this change works for your system, you could make it permanently.
> 
> 5. Reload the sysctl settings.