When you do a test with a lot of remote JMeter slaves, there may be situations when not all remote jmeter-servers were started at the moment master tries to init them. For this situation, the retry behavior is suggested. Additionally, an option to ignore failed slaves suggested. The pull request can be seen here: https://github.com/apache/jmeter/pull/13
Date: Fri Jan 30 09:33:21 2015 New Revision: 1655969 URL: http://svn.apache.org/r1655969 Log: Bug 57500 - Introduce retry behavior for remote testing Added: jmeter/trunk/src/core/org/apache/jmeter/engine/DistributedRunner.java jmeter/trunk/test/src/org/apache/jmeter/engine/DistributedRunnerTest.java Modified: jmeter/trunk/bin/jmeter.properties jmeter/trunk/src/core/org/apache/jmeter/JMeter.java jmeter/trunk/src/core/org/apache/jmeter/engine/ClientJMeterEngine.java jmeter/trunk/src/core/org/apache/jmeter/gui/action/RemoteStart.java jmeter/trunk/xdocs/changes.xml jmeter/trunk/xdocs/usermanual/remote-test.xml
Date: Fri Jan 30 11:08:25 2015 New Revision: 1655987 URL: http://svn.apache.org/r1655987 Log: Bug 57500 - Introduce retry behavior for remote testing / fix test Modified: jmeter/trunk/test/src/org/apache/jmeter/engine/DistributedRunnerTest.java
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3521