That is exactly the issue. Seeing what the "reload" did to the memory
(starting a new worker process) was the culprit. I was thinking the
configuration reload should just refresh what's in memory, but it clearly
doubles the requirement of memory and must wait until the previous child
can stop grace
Hello!
On Fri, Jul 27, 2018 at 10:56:38AM -0400, Shaun Tarves wrote:
> Here are the relevant parts of our configuration:
>
> worker_processes 1;
> pid/var/run/nginx.pid;
> events {
> worker_connections 512;
> }
> http {
> server {
> listen xx.xx.xx.xx:443 default_server ssl;
Here are the relevant parts of our configuration:
worker_processes 1;
pid/var/run/nginx.pid;
events {
worker_connections 512;
}
http {
server {
listen xx.xx.xx.xx:443 default_server ssl;
ssl on;
ssl_certificate /opt/xxx.pem;
ssl_certificate_key /opt/xxx.key
ssl_
FYI - I believe I figured it out. Suggestions welcomed. Here is what I did:
On the frontend: Instead of doing GETs and POSTs to
"api.anothersite.com/api/messages" I now do the call to
"mysite.com/api/messages"
On the backend: added an additional "location" similar to:
location /api/messages {
