Disabling a node in NeoLoad stops it from running tests without removing it from your setup

A node in NeoLoad is a machine that runs load-generation tasks during a test. When you disable a node, NeoLoad removes it from the current test run but keeps it in your configuration for later use. This is useful when you want to troubleshoot a specific machine, perform maintenance, or temporarily reduce the number of load generators without deleting the node entirely.

You disable a node through the NeoLoad interface before or during a test. The process takes seconds and does not affect your test script or other nodes in your setup.

Key Takeaways

  • Disabling a node removes it from the current test run but keeps it saved in your NeoLoad project for future use.
  • You can disable a node in the Machines view by unchecking the checkbox next to the node name before starting a test.
  • A disabled node will not generate load or consume resources during the test, even though it remains part of your configuration.
  • You can re-enable a node at any time by checking the checkbox again before running another test.

Disable a node before starting a test

The most common way to disable a node is to uncheck it in the Machines view before you run a test. Open your NeoLoad project and go to the Machines tab on the left side of the screen. You will see a list of all nodes in your setup, each with a checkbox next to its name.

Find the node you want to disable and uncheck the box beside it. The checkbox will now be empty, and the node name may appear grayed out or dimmed. When you start your test, NeoLoad will skip that node and use only the checked nodes to generate load.

Disable a node during a running test

If you need to disable a node while a test is already running, you can do so from the Runtime view. During a test, the Runtime tab shows all active nodes and their current status. Look for the node you want to remove and right-click on it, or look for a disable or stop option in the interface menu for that node.

The exact steps depend on your version of NeoLoad, but most versions allow you to pause or stop a specific node without stopping the entire test. When you disable a node mid-test, NeoLoad will finish any active transactions on that node and then remove it from load generation for the remainder of the test.

Re-enable a disabled node

To use a disabled node again, go back to the Machines view and check the box next to its name. The node will be included in your next test run. You do not need to reconfigure the node or change any settings — simply checking the box makes it active again.

If you disabled a node during a running test and want to bring it back into that same test, you may need to stop and restart the test. Check your NeoLoad version documentation or the Runtime menu to see if mid-test re-enabling is supported.

Why you might disable a node

Disabling a node is helpful in several situations. If one machine is running slowly or showing errors, you can disable it while you investigate the problem on that machine. If you are testing with fewer load generators to see how your application performs under lighter load, disabling some nodes lets you adjust the test without deleting them. If a node is undergoing maintenance or updates, disabling it keeps it out of your tests until it is ready.

Disabling is also faster than deleting and re-adding a node if you think you will need it again soon. Your node configuration, IP address, and all settings remain intact, so you can turn it back on immediately.

Difference between disabling and deleting a node

When you disable a node, it stays in your NeoLoad project but does not run during tests. When you delete a node, it is removed from your project entirely. If you delete a node and later want to use that machine again, you have to add it back and reconfigure it from scratch.

For temporary situations — maintenance, troubleshooting, or testing with fewer generators — disabling is the better choice. Reserve deletion for nodes you no longer need or plan to replace with a different machine.

Frequently Asked Questions

Does disabling a node affect my test results?

Yes. A disabled node does not generate load, so your total load will be lower than if that node were enabled. If you normally run with five nodes and disable one, you will have 20 percent less load during the test. Plan your test accordingly or adjust your load settings to compensate.

Can I disable a node if a test is already running?

Most versions of NeoLoad allow you to disable a node during a running test through the Runtime view. The node will stop generating new load, though it may finish transactions already in progress. Check your NeoLoad version to confirm this feature is available.

Will a disabled node show up in my test results?

No. Disabled nodes do not appear in the results because they did not participate in the test. Only the nodes that were checked and active during the test will be listed in your results.

What happens if I disable all nodes?

If you disable every node in your setup, NeoLoad will not have any machines to run the test on. The test will not start, or it will fail immediately. Always keep at least one node enabled to run your test.