Description

For databases utilizing Availability Groups with the FileStream feature configured. This wait accumulates while a secondary replica is waiting for the primary to flush all its files. Some values are expected but if values are excessive investigation is required

Resolved by

DBAs and Developers

Suggested solutions

1. If Filestream load is high consider scaling out activity over multiple databases
2. Make sure code and directories have been configured as per FileStream best practices (link below)
3. Check SQL Server error log for any FileStream warnings and errors
4. Upgrade disks hosting the FileStream database and transaction log files

Additional research

FILESTREAM Best Practices
AlwaysOn Availability Groups Troubleshooting and Monitoring Guide

⇐ Back to index