Hi Nirmal, I could not reproduce the error using packs from master build. I checked again for hard-coded references to "is" in both auto-scaler and cartridge agent components but could not find any.
Can you provide us with the deployment policy that you used? Does your deployment have multiple network partitions? As Sajith said, did you happen to re-deploy the cartridges? Or did you face this issue in a fresh deployment? Thanks. On Wed, Jul 9, 2014 at 5:28 PM, Sajith Kariyawasam <[email protected]> wrote: > Hi Nirmal, > > Did you have an "is" cartridge deployed previously deployed without > clustering, and then redeployed a new cartridge with the same name (is), > with clustering enabled.? > I have a feeling that if a cartridge is re-deployed, certain properties > are not properly getting updated in the topology? > > In the meantime, we will go through the code and have a look > > Thanks, > Sajith > > > On Wed, Jul 9, 2014 at 7:57 AM, Nirmal Fernando <[email protected]> wrote: > >> And this is only clustering based deployment and not the worker-mgt >> separation. Since, for IS we don't use that pattern as a practice. >> >> >> On Tue, Jul 8, 2014 at 7:27 PM, Nirmal Fernando <[email protected]> wrote: >> >>> Akila, >>> >>> this is not a puppet issue, since everything works fine after I changed >>> the cartridge type to 'identity' (and changed puppet accordingly). >>> >>> I clearly noticed that when the cartridge type was 'is', hasPrimary was >>> set to false, and when it's 'identity' hasPrimary became true (which is the >>> issue). >>> >>> >>> On Tue, Jul 8, 2014 at 12:11 PM, Akila Ravihansa Perera < >>> [email protected]> wrote: >>> >>>> Hi Nirmal, >>>> >>>> Are you deploying IS as a worker/manager separated setup OR just a >>>> default setup? >>>> >>>> Could you please post debug logs of cartridge agent and agent >>>> extensions log? >>>> >>>> I checked the clustering related code again but could not find any >>>> hard-coded references to 'is' cartridge type. >>>> >>>> My guess is that Puppet is not correctly loading relevant module >>>> because of some conflict with 'is' Puppet module name with some other >>>> module. Have you taken our latest Puppet scripts which includes proper >>>> pattern matching for Puppet module names? >>>> >>>> Correct pattern in is.pp should be as follows; >>>> >>>> node /[0-9]{1,12}.(default|manager|worker).is/ inherits base { >>>> >>>> Thanks. >>>> >>>> >>>> On Wed, Jul 9, 2014 at 12:06 AM, Nirmal Fernando <[email protected]> >>>> wrote: >>>> >>>>> $Subject. which make it impossible to use 'is' as the cartridge type >>>>> with clustering. >>>>> >>>>> Work-around is to use a different name as the cartridge type. >>>>> >>>>> -- >>>>> >>>>> Thanks & regards, >>>>> Nirmal >>>>> >>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>>>> Mobile: +94715779733 >>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Akila Ravihansa Perera >>>> Software Engineer >>>> WSO2 Inc. >>>> http://wso2.com >>>> >>>> Phone: +94 77 64 154 38 >>>> Blog: http://ravihansa3000.blogspot.com >>>> >>> >>> >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> >> > > > -- > *--* > *Sajith Kariyawasam* > *Mobile: +94772269575 <%2B94772269575>* > -- Akila Ravihansa Perera Software Engineer WSO2 Inc. http://wso2.com Phone: +94 77 64 154 38 Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
