Clever Geek Handbook

Error opening timeout (configure client timeout)

I have an application hosted on Openshift. We have functionality that allows the user to upload a file to $ OPENSHIFT_DATA_DIR and then calls the nodeJS function to insert into our DB. For large tables, this operation may take 5-7 minutes.

BUT, before the server completes the operation, the client side will be disconnected and the gateway timeout error message will appear in 120,000ms , the server side process will continue the operation and after a while, it will terminate, but the client side comes with this terrible error.

I need to know where I can edit those 120,000ms. I edited haproxy with different values, but the timeout is still 120 seconds. Is there another file?

retries                 6
timeout http-request    8m
timeout queue           8m
timeout connect         8m
timeout client          8m
timeout server          8m
timeout http-keep-alive 8m

found 2 haproxy files:

  • HAProxy / CONF / HAProxy / haproxy.cfg

  • Haproxy / version / 1.4 / config / haproxy.cfg

both edited

I am assuming there are multiple timeouts but need to know where they are or how to change the timeout on the client side

Gears App: 3

haproxy-1.4 (Web Load Balancer)
 Gears: Located with nodejs-0.10
nodejs-0.10 (Node.js 0.10)
postgresql-9.2 (PostgreSQL 9.2)
   Gears:          1 small
smarterclayton-redis-2.6 (Redis)
+3


source to share


1 answer


5-7 minutes is a very long time for a web request. It looks like this will be a great opportunity for you to explore background tasks. Try downloading data from the client and processing it in the background with something similar to delayed_job in rails.



+1


source






More articles:


All Articles