Apache Web Server accessing Red Hat Storage volume experiences long response times for 404 HTTP_NOT_FOUND
Issue
- While serving web content hosted on an RHS/Gluster volume mounted via the Native Gluster Client, any attempt to access a non-existent file causes an excessive response time before the 404 error is returned
- Accessing existing files is less than 20 milliseconds while 404 errors take 3 or more seconds
- It takes too long to receive a 404 error for missing or non-existent files on Gluster
Environment
- Apache Web Server 2.2 and other versions running on RHEL-6.4 client systems
- Red Hat Storage Server 2.0 Update 5 and 2.1 RC
- First observed on AWS but confirmed outside of AWS
- RHS Configuration: 2 instances/peers, 3 gluster volumes, all Replica 2
- Web content of images and documents of various sizes, thousands of files
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
