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
I have 3 node deployment of EMQX running in aws eks. I am running the emqtt-bench for load testing with
./emqtt_bench conn -h nlbIp -p 1883 -k 60000 -c 50000 -i 30.
I am getting the above error in emqtt-bench.
In the client machine. I have set the below
ulimit -n 200000
sudo sysctl -w net.ipv4.ip_local_port_range="1025 65534"
echo 1000000 > /proc/sys/fs/nr_open
The text was updated successfully, but these errors were encountered:
I guess the LB closed the conn because of idling as you only connect but no sub/pub ops and you also use a very large keep alive timer (60000s) prevents clients to send heartbeat to make the LB decide to keep the TCP alive.
I have 3 node deployment of EMQX running in aws eks. I am running the emqtt-bench for load testing with
./emqtt_bench conn -h nlbIp -p 1883 -k 60000 -c 50000 -i 30.
I am getting the above error in emqtt-bench.
In the client machine. I have set the below
ulimit -n 200000
sudo sysctl -w net.ipv4.ip_local_port_range="1025 65534"
echo 1000000 > /proc/sys/fs/nr_open
The text was updated successfully, but these errors were encountered: