Bug 53894 - Heartbeat function for jMeter running as slave in distributed tests
Summary: Heartbeat function for jMeter running as slave in distributed tests
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.7
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2012-09-19 05:52 UTC by Nils Petzäll
Modified: 2014-07-25 09:41 UTC (History)
3 users (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Nils Petzäll 2012-09-19 05:52:27 UTC

When running distributed tests, if a slave crashes for some reason. The "master" should be notified. Better to fail fast than to keep waiting for a test finished for the slave that will never come.

When starting a test, the slave should report back the start time for the test to the master.

Master saves the start time in relation to the specific slave.
Slave saves the start time for later queries from the master.

After all slaves have reported back the start time. The master will query each slave for the start time.

If the start time differs from the first reported or no response is sent back, master should assume that the slave has been restarted or crashed.

If restarted or crashed, the test should optionally be marked as failed. Atleast the master shouldn't wait for a "test finished" from that slave.

Hearbeat for a slave should be disabled after test finished has been received.

Hearbeat should be optional.

Comment 1 The ASF infrastructure team 2022-09-24 20:37:51 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2933