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
while using nodeload accross many servers (dstributed onto EC2 instances), I saw strange bandwidth collapsing although my scenario was a simple "ramp up".
After investigating, the collapsing was caused by some slaves who went into a strange state :
their cpu usage falls from 40% to almost 0%
they still send data to the master but values are zero...
in the logged output I see : ......WARN: Error during HTTP request: Error: socket hang up......... ................................
tcpdump -i eth0 -An port 80 shows me NOTHING, so the slave is no longer connecting
I think the socket reaches a timeout, but the reconnection code doesn't work, but I'm not a NodeJS expert .
here is my setup :
1 master
15 EC2 slaves running nodeload.js
the tested service is an amazon elastic load balancer with autoscaling group with apache/tomcat servers
the code that I use from the master :
vartrk_test={name: "30min ramp",host: targetHost,port: 80,timeLimit: 1800,loadProfile: [[0,0],[1800,500]],numUsers: 1,stats: [/*..removed stuff..*/],requestGenerator: function(client){/*..removed stuff..*/varrequest=client.request('GET',uri,headers);request.end();returnrequest;}};console.log('\nStarting test.\n');varcluster=newnl.LoadTestCluster('MYPUBLICIP:8601',slaveHosts);// gracefully propagate the interruption to the slavesprocess.on('SIGINT',function(){console.log('\nGot SIGINT. Stopping test\n');cluster.end();});cluster.run(trk_test);cluster.on('end',function(){console.log('\nAll tests done. exiting.\n');process.exit(0);});
Any idea of what happens ?
The text was updated successfully, but these errors were encountered:
Hi
while using nodeload accross many servers (dstributed onto EC2 instances), I saw strange bandwidth collapsing although my scenario was a simple "ramp up".
After investigating, the collapsing was caused by some slaves who went into a strange state :
......WARN: Error during HTTP request: Error: socket hang up......... ................................
tcpdump -i eth0 -An port 80
shows me NOTHING, so the slave is no longer connectingI think the socket reaches a timeout, but the reconnection code doesn't work, but I'm not a NodeJS expert .
here is my setup :
the code that I use from the master :
Any idea of what happens ?
The text was updated successfully, but these errors were encountered: