Print

[kilik]

I have a job whose execution results I don't need. But I want the job execute even in the event of any hardware failure on the client, server or node side.

For client side, setCancelUponClientDisconnect(true) make job still execute even if client disconnects because of hardware failure on the client machine.
For server side, enabling recovery from hardware failures on the nodes.
But what if server machine encounter hardware failure?

[lolo]

Hello,

As you have stated, the JPPF client currently cannot recover from a hard-failure of the server. I have registered a feature requested for this: 3540739 - Client side recovery from hardware failure. Given our current bandwith, I cannot promise this will be implemented anytime soon.
Something you might consider to mitigate the risk of such an event, is the possiblity to persist jobs and their results. We also have a related sample which demonstrates how it works and provides a code sample of an implementation of it.

I hope this helps.

Sincerely,
-Laurent

[kilik]

Hi Laurent,

Thanks for your suggestion. The job recovery sample you mentioned demonstrates the manual recovery, as far as I understand. The client cannot automatically recover job since it cannot detect the broken connection without using heartbeats. Manual recovery is not suitable in some case.
Actually, server become the single point of failure of a JPPF cluster. If there would be a hot-standby server synchronizing server state with the primary server, the server fail-over could take place in the event of server failure.