Compatibility with nginx dyups

[Limur]

Hello. I'm trying to use you module with nginx_dyups. While changing upstream params(add/delete/update) servers also add in POST string you module part config, but nothing...(

For example:
curl -d "server 127.0.0.1:8089;server 127.0.0.1:8088;limit_upstream_conn limit=100 zone=test backlog=10000 timeout=180s;" 127.0.0.1:8081/upstream/dyhost

But while getting params from dyups interface all needed changes shows.

New params simply doesn't work, and module stop working(no limits/queue/etc.)

[cfsego]

please try the updated module in branch 'dyups'

[cfsego]

#14
I added 'instant_hook' parameter to the directive 'limit_upstream_conn'.
you should add this parameter in your POST string.
for example:
curl -d "server 127.0.0.1:8089;server 127.0.0.1:8088;limit_upstream_conn limit=100 zone=test backlog=10000 timeout=180s instant_hook;" 127.0.0.1:8081/upstream/dyhost

[Limur]

You are the best. Thanks a lot!!!.

BTW, one more question - is there any way to...pause/suspend all traffic and then start/resume. Something like set limit=0 to queue all traffic and then change to needed number for normal working.

I tried insomnia. But even with shared memory in LUA it doesn't work as needed. With more than one nginx worker(threads) - they(workers) simply do not undestand command "sleep". May be you have any ideas?

[cfsego]

I think there is nothing wrong with insomnia, probably you have some access phase modules which interfere insomnia

[cfsego]

Comparing to setting limit = 0, I'd prefer to add a particular variable to manipulate pausing / resuming, eg. $limit_ups_pause.
so you can probably do like this:

server {
location / {
set_by_lua $limit_ups_pause "return shared_state.insomnia==true?'1':'0'; ";
}
}

but I do think insomnia should work, so this is only the plan B.

[Limur]

I think there is nothing wrong with insomnia, probably you have some access phase modules which interfere insomnia

Tried with clean LUA and insomnia. All workers didn't want to sleep. With single worker(and master process)- all is ok. Even shared state didn't help(

[cfsego]