Hi Praveen, Thanks for the response and the ticket. Is it possible for you to point me to the opensaf code module where this bug might be?
Thanks! -----Original Message----- From: praveen malviya [mailto:[email protected]] Sent: Monday, May 04, 2015 7:41 AM To: William R Elliott; [email protected] Cc: Lisa Ann Lentz-Liddell; David S Thompson Subject: Re: [users] Problems dynamicly adding new SUs to existing SGs On 04-May-15 10:15 AM, praveen malviya wrote: > > > On 01-May-15 3:11 AM, William R Elliott wrote: >> Hi Praveen, >> We have a common method that calls saAmfHealthcheckStart and we have no >> problems unlocking any service unit in our cluster. Therefore, we are using >> the API correctly. We only have this problem when we try to unlock a >> service unit that was dynamicly added to an existing service group who's >> service units are running in the cluster. I.e. using the example in my >> previous email: >> 1) The cluster (opensaf) processes are running. >> 2) All the SUs in the cluster are unlocked and all associated component >> processes are running including the amfHAFDSU1.1 and amfHAFDSU1.2. >> 3) Using immcfg I added a new SU called amfHAFDSU1.3 to the HAFD sg. >> 4) When I unlock amfHAFDSU1.3 I get the healthcheck start error. >> >> After further testing today, I found out after I dynamicly add amfHAFDSU1.3 >> and I restart the node the amfHAFDSU1.3 components are suppose to start on, >> I can unlock amfHAFDSU1.3 with out errors. Also, I learned after adding >> amfHAFDSU1.3 and executing immdump and redirecting the output in to a file, >> then stop and start the cluster using that file as input, amfHAFDSU1.3 will >> unlock with out errors. >> >> So from what I can observe, it's as if some action such as restarting a node >> or restarting the entire cluster causes a refresh of the internal cluster >> configuration and then the dynamicly added SU wil work correctly. >> >> What do I need to do to get a SU that has been dynamicly added to a >> currently running SG to unlock successfully with out having to restart a >> node, or the entire cluster? >> >> Thanks, > I have checked, there is an issue in amfnd. It is not reading all the > healthcheckkeys for the same comptype in this particular case. > If it is not reported already, I will raise a ticket. > Ticket #1363 for this issue. It is in review state. Thanks, Praveen > Thanks, > Praveen >> >> >> >> >> -----Original Message----- >> From: praveen malviya [mailto:[email protected]] >> Sent: Thursday, April 30, 2015 12:44 AM >> To: William R Elliott; [email protected] >> Cc: David S Thompson; Lisa Ann Lentz-Liddell >> Subject: Re: [users] Problems dynamicly adding new SUs to existing >> SGs >> >> >> >> On 30-Apr-15 4:45 AM, William R Elliott wrote: >>> I am using opensaf 4.4.0. I have a cluster running on two machines both >>> controllers. In this cluster there's an SG called amfHAFDSG1. This SG has >>> two SUs called amfHAFDSU1.1 and amfHAFDSU1.2. Each of these SUs have one >>> component amfHAFDComp1.1.1 and amfHAFDComp1.2.1. When these SUs are >>> unlocked, one HAFD process starts on each machine. The redundancy model is >>> no redundancy. >>> >>> I have a need to dynamicly add an extra SU called amfHAFDSU1.3 to >>> amfHAFDSG1. The objects for amfHAFDSU1.3 are in a file called hafd13.xml >>> (see contents of this file below). >>> I executed the following steps to add amfHAFDSU1.3 to the configuration: >>> >>> 1) immcfg -a saAmfSGNumPrefInserviceSUs=3 >>> safSg=amfHAFDSG1,safApp=olcApp >>> >>> 2) immcfg -v -f hafd13.xml >>> >>> No errors were issued by the immcfg command, immdump shows the amfHAFDSU1.3 >>> objects were added correctly, and the amf-state su command shows the >>> amfHAFDSU1.3 SU is locked for instantiation. However, when I unlock >>> amfHAFDSU1.3, the HAFD process bounces and issues this healthcheck start >>> error: >>> SA_AIS_ERR_NOT_EXIST = 12, >>> >>> This is confusing to me because I can delete the existing SU amfHAFDSU1.2, >>> and use the same exact input (see below xml) file with the exception that >>> the 1.3 is changed to 1.2 and everything works correctly. I.e. the >>> amfHAFDSU1.2 objects are added to the configuration and amfHAFDSU1.2 >>> unlocks with out errors. This only happens when I'm dynamicly adding a new >>> SU. >>> >>> I would appreciate any help solving this problem. >>> >>> Thanks >>> >>> Here's the input file I'm using: >>> <?xml version="1.0" encoding="UTF-8"?> <imm:IMM-contents >>> xmlns:imm="http://www.saforum.org/IMMSchema"; >>> xsi:noNamespaceSchemaLocation="SAI-AIS-IMM-XSD-A.01.01.xsd" >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> >>> <!-- AMF Service Instance amfHAFDSI1.3 --> >>> <object class="SaAmfSI"> >>> <dn>safSi=amfHAFDSI1.3,safApp=olcApp</dn> >>> <attr> >>> <name>saAmfSIRank</name> >>> <value>1</value> >>> </attr> >>> <attr> >>> <name>saAmfSvcType</name> >>> >>> <value>safVersion=v1,safSvcType=siBaseTypeNRRedundancy</value> >>> </attr> >>> <attr> >>> <name>saAmfSIProtectedbySG</name> >>> <value>safSg=amfHAFDSG1,safApp=olcApp</value> >>> </attr> >>> </object> >>> <!-- AMF Service Unit safSu=amfHAFDSU1.3 --> >>> <object class="SaAmfSU"> >>> <dn>safSu=amfHAFDSU1.3,safSg=amfHAFDSG1,safApp=olcApp</dn> >>> <attr> >>> <name>saAmfSURank</name> >>> <value>1</value> >>> </attr> >>> <attr> >>> <name>saAmfSUFailover</name> >>> <value>1</value> >>> </attr> >>> <attr> >>> <name>saAmfSUAdminState</name> >>> <value>3</value> >>> </attr> >>> <attr> >>> <name>saAmfSUType</name> >>> <value>safVersion=v1,safSuType=suBaseTypeNRRedundancy</value> >>> </attr> >>> <attr> >>> <name>saAmfSUHostNodeOrNodeGroup</name> >>> >>> <value>safAmfNode=siamang.monkey.lab,safAmfCluster=PA2BE</value> >>> </attr> >>> </object> >>> <!-- AMF Component Service Instance amfHAFDCompCSI1.3.1--> >>> <object class="SaAmfCSI"> >>> >>> <dn>safCsi=amfHAFDCompCSI1.3.1,safSi=amfHAFDSI1.3,safApp=olcApp</dn> >>> <attr> >>> <name>saAmfCSType</name> >>> <value>safVersion=v1,safCSType=amfHAFDCompCSType</value> >>> </attr> >>> </object> >>> <!-- AMF Component amfHAFDComp1.3.1--> >>> <object class="SaAmfComp"> >>> >>> <dn>safComp=amfHAFDComp1.3.1,safSu=amfHAFDSU1.3,safSg=amfHAFDSG1,safApp=olcApp</dn> >>> <attr> >>> <name>saAmfCompInstantiateTimeout</name> >>> <value>45000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfCompNumMaxInstantiateWithoutDelay</name> >>> <value>2</value> >>> </attr> >>> <attr> >>> <name>saAmfCompNumMaxInstantiateWithDelay</name> >>> <value>3</value> >>> </attr> >>> <attr> >>> <name>saAmfCompDelayBetweenInstantiateAttempts</name> >>> <value>2000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfCompCleanupTimeout</name> >>> <value>15000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfCompNumMaxAmStartAttempts</name> >>> <value>2</value> >>> </attr> >>> <attr> >>> <name>saAmfCompNumMaxAmStopAttempts</name> >>> <value>2</value> >>> </attr> >>> <attr> >>> <name>saAmfCompCSISetCallbackTimeout</name> >>> <value>8000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfCompCSIRmvCallbackTimeout</name> >>> <value>8000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfCompInstantiateCmdArgv</name> >>> <value>PA2BE</value> >>> </attr> >>> <attr> >>> <name>saAmfCompType</name> >>> <value>safVersion=v1,safCompType=amfHAFDCompBaseType</value> >>> </attr> >>> </object> >>> <object class="SaAmfCompCsType"> >>> >>> <dn>safSupportedCsType=safVersion=v1\,safCSType=amfHAFDCompCSType,safComp=amfHAFDComp1.3.1,safSu=amfHAFDSU1.3,safSg=amfHAFDSG1,safApp=olcApp</dn> >>> <attr> >>> <name>saAmfCompNumMaxActiveCSIs</name> >>> <value>1</value> >>> </attr> >>> <attr> >>> <name>saAmfCompNumMaxStandbyCSIs</name> >>> <value>1</value> >>> </attr> >>> </object> >>> <!-- AMF Component HealthCheck amfHAFDComp1.3.1--> >>> <object class="SaAmfHealthcheckType"> >>> >>> <dn>safHealthcheckKey=amfHAFDCompHCKey1.3.1,safVersion=v1,safCompTyp >>> e= >>> amfHAFDCompBaseType</dn> >> >> In the API saAmfHealthcheckStart( >> SaAmfHandleT amfHandle, >> const SaNameT *compName, >> const SaAmfHealthcheckKeyT *healthcheckKey, >> SaAmfHealthcheckInvocationT invocationType, >> SaAmfRecommendedRecoveryT recommendedRecovery); >> >> In the third argument pass the configured rdn value of SaAmfHealthcheckType >> i.e "amfHAFDCompHCKey1.3.1". >> >> Thanks, >> Praveen >>> <attr> >>> <name>saAmfHctDefPeriod</name> >>> <value>4000000000</value> >>> </attr> >>> <attr> >>> <name>saAmfHctDefMaxDuration</name> >>> <value>8000000000</value> >>> </attr> >>> </object> >>> </imm:IMM-contents> >>> >>> >>> >>> >>> ________________________________ >>> The information transmitted herein is intended only for the person or >>> entity to which it is addressed and may contain confidential, proprietary >>> and/or privileged material. Any review, retransmission, dissemination or >>> other use of, or taking of any action in reliance upon, this information by >>> persons or entities other than the intended recipient is prohibited. If you >>> received this in error, please contact the sender and delete the material >>> from any computer. >>> -------------------------------------------------------------------- >>> -- >>> -------- One dashboard for servers and applications across >>> Physical-Virtual-Cloud Widest out-of-the-box monitoring support with >>> 50+ applications Performance metrics, stats and reports that give >>> 50+ you >>> Actionable Insights Deep dive visibility with transaction tracing >>> using APM Insight. >>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>> _______________________________________________ >>> Opensaf-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/opensaf-users >>> >> >> >> ________________________________ >> The information transmitted herein is intended only for the person or entity >> to which it is addressed and may contain confidential, proprietary and/or >> privileged material. Any review, retransmission, dissemination or other use >> of, or taking of any action in reliance upon, this information by persons or >> entities other than the intended recipient is prohibited. If you received >> this in error, please contact the sender and delete the material from any >> computer. >> > > ---------------------------------------------------------------------- > -------- One dashboard for servers and applications across > Physical-Virtual-Cloud Widest out-of-the-box monitoring support with > 50+ applications Performance metrics, stats and reports that give you > Actionable Insights Deep dive visibility with transaction tracing > using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Opensaf-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensaf-users > ________________________________ The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
