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

NotAllAgentsAvailable Exception Thrown With Many Agents #489

Closed
kweinberg1 opened this issue Oct 7, 2022 · 2 comments
Closed

NotAllAgentsAvailable Exception Thrown With Many Agents #489

kweinberg1 opened this issue Oct 7, 2022 · 2 comments
Labels
bug Something isn't working v4

Comments

@kweinberg1
Copy link

To appropriately test the systems under load, we have controllers with 45+ machines backing behind them.

It is very common to run an NBomber test with 45 agents to fail because NBomber is unable to connect all to all of them. The test doesn't often begin and developers are faced with an NotAllAgentsAvailable exception.

To reproduce this, we can create a basic NBomber test application with one scenario that does nothing. Spawn many agent processes on multiple machines. We will encounter this problem about 50% of the time with 45 agents and 100% of the time with 135 agents (3 agents per machine).

This makes scaling our tests to the target load nearly impossible.

@AntyaDev
Copy link
Contributor

Hi @kweinberg1

I started working on this.
I will keep you informed.

@AntyaDev AntyaDev added bug Something isn't working v4 labels Oct 30, 2022
@AntyaDev
Copy link
Contributor

AntyaDev commented Nov 3, 2022

Hi @kweinberg1 ,

I have fixed this issue in NBomber Cluster 4.0.0-beta3

@AntyaDev AntyaDev closed this as completed Nov 3, 2022
@AntyaDev AntyaDev reopened this Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v4
Projects
None yet
Development

No branches or pull requests

2 participants