JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Feature request JPPF-9  -  Change the JPPF configuration based on observable behavior
Posted Aug 08, 2012 - updated Mar 21, 2019
icon_info.png This issue has been closed with status "Closed" and resolution "WON'T FIX".
Issue details
  • Type of issue
    Feature request
  • Status
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
    Management / Monitoring
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png Abandoned
Issue description

From this forum thread "Is there a way to have the load balancing mechanism automatically remove a task from an unresponsive node and give it to another?"

This is about giving the ability to adapt the configuration and topology of a JPPF network, based on the observable behavior of the servers and nodes, by providing the following: - notifications of events occurring on the server or node side: execution performance events, lifecycle events, JVM events, user-defined events such as user-defined threshold crossing, etc... - capability to take action based on these events: start / stop nodes, start/stop servers, send alerts, execute some script/application, etc...

This requires the definition of a notification mechanism that is consistent accross JPPF components as well as accross the type of events to be observed, and adding new management capabilities in order to take appropriate actions.

Comment posted by
Mar 21, 19:24
JPPF has had the abilities requested here for some time now, making this featutre request irrelevant. It will be closed accordingly.