ras-wrapper.conf flag : worker.restart.on.recovery
The RAS of our environment restart regularly due to the flag "wrapper.java.additional.25 = -Dcloudslang.worker.restart.on.recovery" which is set to true in the ras-wrapper.conf.
- We are in HPE-OO V10.70 in On Premise installation
- Could you tell us What impact will we have if we set this flag to false, is there a risk of system instability?
Thanks for your responses
Thank you for contacting MicroFocus Forum.
My name is Carlos Robles, I am from the OO/CSA team.
Regarding your question, if a worker falls, this one would not restart automatically and the workload will be distributed to other workers and performace would be affected it the workload is very big.
Carlos Robles Rojas
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
Thank you for response, but when a worker makes a recovery, like this example:
04:41:41,719 [local-scheduler-persisted_Worker-8] (WorkerRecoveryServiceImpl.java:70) WARN - Worker : xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is non responsive! Worker recovery is started.
04:41:41,721 [local-scheduler-persisted_Worker-8] (WorkerRecoveryServiceImpl.java:92) WARN - Worker [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] is going to be recovered
04:41:41,748 [local-scheduler-persisted_Worker-8] (WorkerRecoveryServiceImpl.java:108) WARN - Worker [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] recovery is done in 27 ms
the worker does not fall. The worker falls because of the choice :
04:35:05,321 [scoreWorkerScheduler-1] (WorkerRecoveryManagerImpl.java:52) WARN - Worker is configured to restart on recovery and since internal recovery is needed the process is exiting...
So should we systematically choose the reboot.on.recovery?
if we do not set this flag on true, what is the risk?
Autooa - Marc GAGNARD