openresty / openresty/lua-nginx-module

Test ab fails after 100 connections with many workers tarantool

Open
#2,156 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
11.8k
Forks
2.1k
Avg merge
6h 1m
Merged PRs (30d)
6

Description

This place is for bug reports and development discussions only. For general questions and
discussions, please join the openresty-en mailing list instead: https://openresty.org/en/community.html

Ensure you have provided the following details while reporting a problem:

  • The exact version of the related software, including but not limited to the OpenResty version
    (if any), the NGINX core version, the ngx_lua module version,
    and your operating system version.
  • A minimal and standalone test case that others can easily run on their side and
    reproduce the issue you are seeing.
  • Do not simply say "something is broken" or "something does not work". Always provide
    as much details as possible. Always describe the symptoms and your expected results.
  • You can (temporarily) enable the nginx debugging logs to see the internal workings
    of NGINX in your nginx''s error.log file. See http://nginx.org/en/docs/debugging_log.html
    The same instructions apply equally well to OpenResty.
  • If you are seeing crashes, please provide the full backtrace for the crash. See
    https://www.nginx.com/resources/wiki/start/topics/tutorials/debugging/#core-dump
    for more details.

Please, do not use Chinese here. This place is considered English only. If you
really want to use Chinese, please join and post to the openresty (Chinese)
mailing list instead. Please see https://openresty.org/en/community.html Thanks for
your cooperation.

Hi, trying to test with ab on tarantool I noticed that if I put only one worker in the openresty configuration the test doesn't fail instead if I put more workers, having more CPUs, the test fails after 100,000 connections. Can you give me an explanation?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files or tests and does not provide software versions or a standalone reproducer. Start by reproducing the ab test against tarantool with one worker and then multiple workers, while checking nginx's error.log with debugging enabled. Done means the failure after 100,000 connections is reproducible and its cause and expected behavior are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, nginx
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.