Issue description
We recently encountered a bug:
when reuseport is enabled by default, during the running of APISIX, modify config.yaml and start without stopping APISIX. This resulted in some workers still using the old config, some workers using the new config,
and the old workers could not be killed by apisix stop
I think we need to fix it by:
-
When running apisix start, Check if APISIX has been running. If is running, remind to use apisix reload
-
apisix reload needs to regenerate nginx.conf according to config.yaml and then reload
-
When running apisix start or apisix reload , check the nginx.conf syntax before truely run the command.
Environment
- apisix version (cmd:
apisix version):
1.3
- OS:
centos7
Minimal test code / Steps to reproduce the issue
- apisix start
- change conf/config.yaml
- apisix start
Issue description
We recently encountered a bug:
when reuseport is enabled by default, during the running of APISIX, modify
config.yamland start without stopping APISIX. This resulted in some workers still using the old config, some workers using the new config,and the old workers could not be killed by
apisix stopI think we need to fix it by:
When running
apisix start, Check if APISIX has been running. If is running, remind to useapisix reloadapisix reloadneeds to regenerate nginx.conf according to config.yaml and then reloadWhen running
apisix startorapisix reload, check the nginx.conf syntax before truely run the command.Environment
apisix version):1.3
centos7
Minimal test code / Steps to reproduce the issue