The current Disabling ARR prevents moving to another host after a host when failure.
But we need new behavior to Disabling ARR - "A instance is moved to another healthy host . But it is not automatically restarted.
When a host is failed, we don't want to wait until it is repaired. Therefore, we don't want to use Hard-Pin.
However, after an automatic restart, there are cases we simply don't want to release the services to end users.
EX, if a host failure occurs during a night batch period, we will need to check the recovery point and re-run the batch before releasing services.
Even during daytime disruptions, it is necessary to distinguish between committed and non-committed transactions.
If a VM is moved to another healthy host, we can immediately these processes after a host failure.
| Idea priority | Medium |
| Needed By | Quarter |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.