How to let client go and process request further?

roman.alexandr · 2016-03-20T07:40:59+00:00

Hi,Ok, well if the nginx proxy features fit your requirements, then that's all good, but I'd still really like to understand these problems better. W...

How to let client go and process request further?

roman.alexandr

Hi folks!

One more dumb question from me ;)

I have application that process request in order:

1. Authorize user

2. Process data we got from user

3. Saving data to MySQL

4. Saving data to Redis

5. Send message to RabbitMQ.

How can I close connection with user between steps 1 and 2?

I don't want keep client wait while we finish routines. Makes sense?

tahmi.hamza

it's better to do the following :

* send message to RabbitMQ
* end the connection with the user

* mysql / Redis consume the data/msg from RabbitMQ directly

On Sunday, March 20, 2016 at 12:40:59 AM UTC+1, Alexandr Roman wrote:

Hi folks!

One more dumb question from me ;)

I have application that process request in order:
1. Authorize user
2. Process data we got from user
3. Saving data to MySQL
4. Saving data to Redis
5. Send message to RabbitMQ.

How can I close connection with user between steps 1 and 2?
I don't want keep client wait while we finish routines. Makes sense?

roman.alexandr

Thanks for clue. I'll dig deeper into sql consumer for rabbitmq.

Can you please explain how can I "end user connection" and keep process request?

On Sunday, March 20, 2016 at 1:36:21 AM UTC-4, hamza t wrote:

it's better to do the following :

* send message to RabbitMQ
* end the connection with the user
* mysql / Redis consume the data/msg from RabbitMQ directly

On Sunday, March 20, 2016 at 12:40:59 AM UTC+1, Alexandr Roman wrote:
Hi folks!

One more dumb question from me ;)

I have application that process request in order:
1. Authorize user
2. Process data we got from user
3. Saving data to MySQL
4. Saving data to Redis
5. Send message to RabbitMQ.

How can I close connection with user between steps 1 and 2?
I don't want keep client wait while we finish routines. Makes sense?

tahmi.hamza

you just need to push the msg to rabbitMQ when you process the user's request ( you don't need to wait for rabbitMQ to finish anything ) , the rest of the processing can be handled by a separated app that take the msgs from rabbitMQ queue and process them

On Sunday, March 20, 2016 at 7:36:23 PM UTC+1, Alexandr Roman wrote:

Thanks for clue. I'll dig deeper into sql consumer for rabbitmq.
Can you please explain how can I "end user connection" and keep process request?

On Sunday, March 20, 2016 at 1:36:21 AM UTC-4, hamza t wrote:
it's better to do the following :

* send message to RabbitMQ
* end the connection with the user
* mysql / Redis consume the data/msg from RabbitMQ directly

On Sunday, March 20, 2016 at 12:40:59 AM UTC+1, Alexandr Roman wrote:
Hi folks!

One more dumb question from me ;)

I have application that process request in order:
1. Authorize user
2. Process data we got from user
3. Saving data to MySQL
4. Saving data to Redis
5. Send message to RabbitMQ.

How can I close connection with user between steps 1 and 2?
I don't want keep client wait while we finish routines. Makes sense?

jonathan

On Sunday, March 20, 2016 at 2:36:23 PM UTC-4, Alexandr Roman wrote:

Can you please explain how can I "end user connection" and keep process request?

You don't want to do that (or can't do that).

hamza t is saying that you should send all relevant information into Rabbit MQ, then end the request. RabbitMQ won't be able to access the request, just whatever data you send it. This is the standard way across most webservers -- you messsage out any necessary info for post-processing, then end the request.

doujiang24

Hello，

Another simpler way: use ngx.timer.at[1], for example

but be careful for the lua_max_pending_timers and lua_max_running_timers[2]

content_by_lua_block {

authorize_user()

local data = "">

local function send_data_to_backend(premature, data)

save_to_mysql(data)

save_to_redis(data)

send_to_rabbitmap(data)

end

local ok, err = ngx.timer.at(0, send_data_to_backend, data)

if not ok then

ngx.log(ngx.ERR, "failed to create timer: ", err)

end

send_ok_to_client()

}

1. https://github.com/openresty/lua-nginx-module/#ngxtimerat

2. https://github.com/openresty/lua-nginx-module/#lua_max_pending_timers

2016-03-21 4:16 GMT+08:00 <jon...@findmeon.com>:

On Sunday, March 20, 2016 at 2:36:23 PM UTC-4, Alexandr Roman wrote:
Can you please explain how can I "end user connection" and keep process request?

You don't want to do that (or can't do that).

hamza t is saying that you should send all relevant information into Rabbit MQ, then end the request. RabbitMQ won't be able to access the request, just whatever data you send it. This is the standard way across most webservers -- you messsage out any necessary info for post-processing, then end the request.

.