Version 8.3
Our servers sometimes are not very stable. Many times, the host that Perform maintenance job went down and the task stuck pending for hours. Is it possible to configure IIQ to automatically switch to the available server to run the task?
are running the task by specifying the server … I believe you do not specify the server then it will run automatically on the available server.
I doubt we can switch servers if the task is stuck. Have you examined the logs to identify what’s causing it to hang? Perhaps it’s worth considering splitting the configured options into multiple PRISM tasks to see if that resolves the issue.
we didn’t specify host name for the task… during the running of this task, the host went down (due to various reasons like JVM, memory or capacity issues) and task got stuck. Is there anyway for IIQ to automatically switch to run it on another host?
we can’t switch automatically OOTB, however you can implement some some Run Rule task which continuously monitors the long running task and then kill that task and again restart the task … however there would be still issues with run rule task i.e. if this custom is running on server which gets down then it won’t kill the task and won’t be able to restart it.
If a server crashes and is restarted with IIQ, IIQ will reset the last running task and you will see this as a canceled task.
Maybe is this an option for you in combination with automatic restart.
This must done with a ‘generic’ task.
–
We run in a kubernetes cluster, and sometimes Im able to crash our dev-environment, then i see this behavior. 
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.