JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-24  -  Ability to deactivate a node
Posted Aug 08, 2012 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
We propose the possibility to render nodes inactive, without terminating them. This would basically mean that the server would just stop sending tasks to this node until it is activated again. Management and monitoring of the node would still be possible while it is inactive. This would enable additional flexibility from a toplogy point of view.

For example, let's say we have a computer with 4 CPUs and 4 nodes started on this machine. Depending on the kind of job that is executed on the grid, it would be very easy to switch from a topology with 1 node active with 4 processing threads, to one with 4 nodes active with 1 processing thread each, or any combination in-between. Dormant nodes could be reactivated very quickly, as this would only involve setting a flag on the server to let it send tasks to the activated nodes again.

Comment posted by
Dec 22, 00:00
Implemented in SVN trunk revision 2581

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.