问题原文
原帖链接 · Naftuli Kay · CC BY-SA 3.0
I'm using NGINX 1.8.1 on CentOS 6 and 7. During our deploys, it is required that NGINX is stopped, the deploy executes, and NGINX starts again. Unfortunately, NGINX during a stop seems to just 500 all connections. As I'm using Ansible to update 2/10 hosts at a time, it's likely therefore that many of our clients will get 500'd throughout our deploy process.
Is there a way via NGINX settings to have the NGINX process drain all live connections (ie wait for them to complete) while rejecting all new connections during a stop?
I know that Amazon's Elastic Load Balancers do have this functionality, is there an equivalent for NGINX?
社区高分解答
原帖链接 · gxx · CC BY-SA 3.0
According to the comments, you could try to solve this using a firewall:
Task: Block incoming new connections, but keep related and established ones
Try:
iptables -I INPUT -j DROP -p tcp --syn --destination-port 80(or 443, whatever applies to your setup) to set the rule, thus blocking new trafficDo your deployment...
Try:
iptables -D INPUT -j DROP -p tcp --syn --destination-port 80(or 443, whatever applies to your setup) to revert the rule, thus allowing new trafficNote: I've just tested this shortly, it worked as expected. But: Please don't take this for granted, and test for yourself as well. Feedback welcome...
Edit: As @Guntram Blohm pointed out in the comments, better to use iptables -I instead of iptables -A. Changed this appropriately in the above code.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
