Forum Discussion

allaboutunix's avatar
10 years ago

mnt_app resource failover

Hi,   Below is the resource dependecies in my enviroment, what happened is somebody unmount the /app filesystem.So, resource went on faulted state, when i checked that resource criticality i...
  • Sunil_Yadav's avatar
    10 years ago

    Hi,

    Before digging into this particular configuration, lets understand relationship between “criticality of resources” and “failover of SG”.

    Critical resource: Fault of resource will always initiate failover of service group.

    Non-critical resource: Fault of resource will trigger failover of service group only if there is a “critical” AND “online” parent resource up in the dependency tree. Critically of child resources isn’t considered while deciding to failover or not to failover.

    1st query : If parent is set as critical and child is non-critical 0, do it failover to another node.

    If critical parent resource faults, undoubtedly failover will be initiated. If critical parent resource is online and non-critical resource faults, failover will be initiated. If critical parent resource is offline and non-critical resource faults, failover will not be initiated.

    2nd query : If child is set as critical or parent as non-critical 0, then it failover?

    If critical child resource faults, undoubtedly failover will be initiated. If non-critical parent resource faults, failover will not be initiated.

    Based on the "hares -dep" output snippet, the resources dependency tree is like

    APP_aphelion                   APP_tibjmsd                      Blind_check_stopDB

    |                                              |                                              |

    |                                              |                                              |

    |----------------------------------------------|----------------------------------------------|

                                                   |

                                               mnt_app(non-critical)

                                                   |

                                                   |

                                              vol_app(critical)

                                                   |

                                                   |

                                              app_dg(critical)

    As not mentioned, we are assuming that APP_aphelion, APP_tibjmsd, and Blind_check_stopDB are critical resources.

    In this configuration; fault of app_dg, vol_app, APP_aphelion, APP_tibjmsd, or Blind_check_stopDB will initiate failover of the service group. Fault of mnt_app will trigger failover ONLY IF any of APP_aphelion, APP_tibjmsd, or Blind_check_stopDB is online. In all other cases, fault of mnt_app will not trigger failover of the service group.