Environment

Affected versions:

• Yugabyte DB 2.6.1

Fixed in:

• 2.6.2

Issue

Frequent WARN messages in the tserver logs as below

W1009 11:24:45.332646 13528 acceptor.cc:158] Acceptor: accept failed: Network error (yb/util/net/socket.cc:353): accept4(2) error: Resource temporarily unavailable (system error 11)
W1009 11:25:50.299014 13528 acceptor.cc:158] Acceptor: accept failed: Network error (yb/util/net/socket.cc:353): accept4(2) error: Resource temporarily unavailable (system error 11) 

Cause

A regression caused the interpreting of retryable accept failures to stop in Linux. 

Solution

The WARN messages can be ignored and do not cause any performance issues. The issue is fixed in Yugabyte DB 2.6.2. 

The GitHub issue details are available here