Thanks Praveen. For scenario " when both the controllers are down", since Payloads are up and running fine, is there a way around to isolate both the controllers from cluster intentionally or accidentally with sacrificing service availability temporarily. Since actual service is being provided payload nodes, it would be nice to run payload nodes all times. Rebooting payload nodes technically sounds OK, however, I am looking at an way to remove this binding for a specific scenario.
OpenSAF version being used 4.3.0. Best, Greg On Sun, Sep 8, 2013 at 9:29 PM, praveen malviya <[email protected]>wrote: > Please see inline. > > Thanks > Praveen > > On 08-Sep-13 10:31 PM, Greg Hurlman wrote: > >> Hi Folks, >> >> While integrating OpenSAF I faced couple of issues. Can somebody help me, >> if through some way these configurations are possible, >> >> 1. Isolating controller nodes by making the controller service down or n/w >> down once the payload nodes with SUs up and running fine. >> >> I expect here that it should not reboot the payload nodes which are >> running >> fine. This isolation may be temporary though and may be controllers will >> be >> join back to the cluster. >> > If you are isolating only one controller then payloads will not reboot. If > both the controllers are down then payloads will also go down. > > 2. When the first amf-adm unlock/in command fails for some valid reason, >> while starting a particular SU with admin state as locked-instantiation, >> then the subsequent amf-adm unlock/in also fails with reason pending. >> >> Currently I stop the service in payloads and restarts the service in >> controller to try re-instantiating the same SU with amf-adm unlock/in >> command to make it successful second time. Assuming the failure reason is >> fixed before running second time. But stopping services all trough cluster >> and starting again to forget the previous failure is not very encouraging. >> > When "amf-adm unlock-in" fails with repair pending then SU would move to > INSTANTIATION_FAILED state. > Here admin needs to the correct the problems which are generally > associated with component binary or instantiation scripts or bundle path. > After correcting this issue "amf-adm repaired <su dnname>" to repair the > su. In this way components will be instantiated without rebooting cluster. > > 3. While component restart/SU restart is happening in payload node because >> of the configured component recovery action, service opensafd >> stop(intentional) in PL node does not stop the service. Eventually, the >> escalated recovery action reboots the PL node. >> > For this can you specify the version of OpenSAF being used in the system. > >> Best, >> Greg >> ------------------------------**------------------------------** >> ------------------ >> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! >> Discover the easy way to master current and previous Microsoft >> technologies >> and advance your career. Get an incredible 1,500+ hours of step-by-step >> tutorial videos with LearnDevNow. Subscribe today and save! >> http://pubads.g.doubleclick.**net/gampad/clk?id=58041391&iu=** >> /4140/ostg.clktrk<http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk> >> ______________________________**_________________ >> Opensaf-users mailing list >> Opensaf-users@lists.**sourceforge.net<[email protected]> >> https://lists.sourceforge.net/**lists/listinfo/opensaf-users<https://lists.sourceforge.net/lists/listinfo/opensaf-users> >> > > ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
