[RTFACT-16906] default keepalive settings in our nginx container not sufficient to handle heavy workloads Created: 08/Jun/18 Updated: 28/Nov/18 Resolved: 28/Nov/18
|Project:||Artifactory Binary Repository|
Canonical-Kubernetes on AWS
In Kubernetes cluster, (canonical kubernetes on AWS), soldev-qa runs stress tests (like creating 1000 groups, 2000 users etc).
With artifactory 6.0 installed from helm (from stable/artifactory-ha), these tests fail around 200 or so and the error is usually HTTP_EMPTY_RESPONSE. Increasing ELB timeout or ELB connection draining timeouts do not have any effect. Setting keepalive_timeout to 0 and keepalive_requests to 0 (disable keepalive completely) solves this problem for us.
This may have an adverse effect on performance. The solution recommended by Nginx support team was to leave the keepalive_timeout to the default value of 65 seconds, but change the keepalive_requests to the maximum supported value 2147483647 for 32-bit and 4294967295 for 64-bit platform). This should ensure that the requests in keepalive do not get closed by nginx and elb will not get empty response.
|Comment by Ankush Chadha [ 22/Jun/18 ]|
The only change i.e. still open is to update timeout value in artifactory.conf to 2400s from 900 to be consistent with a production version of nginx.conf