Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

curieproxy-nginx Configuration changes partially take effect under multi-core #1236

Open
lqglqy opened this issue Jun 2, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@lqglqy
Copy link

lqglqy commented Jun 2, 2023

Describe the bug
After issuing a global blocking policy, only some requests are blocked.

To Reproduce
Steps to reproduce the behavior:

  1. Configure a simple blocking strategy, for example: the parameter name is test, the parameter value is block, set blocking and avtive.
  2. Publish changes.
  3. used wrk test it, for example: ./wrk -t4 -c100 -d30s -R2000 --latency http://curie.demo:31081/?test=block
  4. View results show that all blocks are not blocked

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Centos7 Docker-compose
  • Version: images tags: main

Additional context
I think the problem should be in the dynamic update implementation of nginx. When reloading config through port 8998, only one worker process is notified. In a multi-core environment, other processes that have not received the update request will not trigger the update.

@lqglqy lqglqy added the bug Something isn't working label Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant