For databases utilizing Availability Groups with the FileStream feature configured. This wait accumulates while the transport manager is waiting for a read/write lock on itself. This wait is uncommon but some small values may detected during startup and shutdown. If values are excessive further investigation is required.
DBAs and Developers
- If Filestream load is high consider scaling out activity over multiple databases
- Make sure code and directories have been configured as per FileStream best practices (link below)
- Check SQL Server error log for any FileStream warnings and errors
- Upgrade disks hosting the FileStream database and transaction log files