will passenger continue to serve the request, when nginx terminates connection through timeout?

[Sivalingam S]

We are running rails app in passenger+nginx, nginx has timeout of 1 minute, whereas in newrelic, we can see the long running SQL query has ran for more than 3 minutes.
Nginx had terminated the connection due to request timeout.

Can passenger run the request even after nginx terminated the request because of timeout?

We are running rails in passenger as nginx integration mode.

[Daniel Knoppel]

If a request times out, Passenger lets your application know (connection half close).

SQL queries are not run by Passenger but by your application and the database. I can imagine that the database just keeps running the query for however long it takes, unless the application does something special to kill it (which, depending on the database, may not even be supported).

- Daniel

[Sivalingam S]

hi Daniel Knoppel,
We are using MySQL. I want the whole request to be killed after the request timeout in nginx. How to achieve that?
Instead of half close, I want the request to be terminated in passenger. So that i can avoid stale passenger process.

[Daniel Knoppel]

Passenger has the max_request_time option to prevent stale application processes:

https://www.phusionpassenger.com/library/config/nginx/reference/#passenger_max_request_time

- Daniel

[Sivalingam S]

Thanks Daniel Knoppel,

passenger_max_request_time option turns out to be available only in enterprise edition.
Our app server is Ruby on Rails, how to get the trigger for half closed connection inside rails app.
Is their any way to identify and kill the request inside app server?