You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When benchmarking a slew of hosts, the swarm-bench tool has been extremely helpful to determine how "ready" a host is to accept a ton of containers executing a workload.
However i've found it to be rather consistent about one in every five runs yields a panic
panic: API error (500): Container created but refresh didn't report it back
This is using the latest version of swarm-bench in master, against a docker-machine provisioned swarm-cluster, and a juju deployed swarm cluster. Both of which are three node swarm clusters, with a single manager.
The text was updated successfully, but these errors were encountered:
When benchmarking a slew of hosts, the swarm-bench tool has been extremely helpful to determine how "ready" a host is to accept a ton of containers executing a workload.
However i've found it to be rather consistent about one in every five runs yields a panic
panic: API error (500): Container created but refresh didn't report it back
This is using the latest version of swarm-bench in master, against a docker-machine provisioned swarm-cluster, and a juju deployed swarm cluster. Both of which are three node swarm clusters, with a single manager.
The text was updated successfully, but these errors were encountered: