Hi Rasanjaya, Yes, but those you mentioned may not be the only case where we need to restart the server. If a lib file is copied or removed that will need a restart as well. But for some files that may not be needed.
Previously how did you track whether new patches were applied or existing patches were removed from Puppet side? Do we have to specify each patch number in Puppet manifest or Hiera? Thanks. On Fri, Jul 22, 2016 at 2:17 PM, Rasanjaya Subasinghe <rasanj...@wso2.com> wrote: > Hi all, > > In general, we can use a bash Init file to maintain the wso2 server state, > which file is supposed to start, stop and restart the wso2 service based on > the configuration change on the master side. We can notify the service unit > file, though puppet relationship to restart the service for any template > change or new patch. > > Thanks > > On Fri, Jul 22, 2016 at 1:24 PM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi, >> >> >>> 3. Each and every time the config file change [Ex: axis2.xml] product >>>> gets deleted and start with the fresh configuration. >>>> >>> >>> ​Agree! It should not start from the beginning for a configuration >>> change. >>> >> >> This is now fixed in master branch. Basically Puppet runs in "refresh" >> mode by default. It will kill any running WSO2 process before applying >> configurations but will use the same pack if it has been already downloaded >> from Puppet master. Also it will apply new configurations on top of >> previous installation if it exists. You can control this behavior by >> setting "wso2::maintenance_mode" Hiera property. If you set it to "new" >> then any previous installation will be cleaned first; "zero" will clean the >> pack as well. >> >> However, we still need to improve on how product server is restarted; >> i.e. the server should be restarted only if there has been a change applied >> to template, patch list is updated, lib files are updated etc. But I don't >> think we can reliably detect (from Puppet side) whether server should be >> restarted or not. Perhaps a template change may not need a restart. So IMO, >> it's better to restart the server on every Puppet run. Any thoughts? >> >> Thanks. >> >> -- >> Akila Ravihansa Perera >> WSO2 Inc.; http://wso2.com/ >> >> Blog: http://ravihansa3000.blogspot.com >> > > > > -- > -------------------------------------------------- > Rasanjaya Subasinghe > Software Engineer, Dev/Ops , WSO2 inc(Sri Lanka) > +94772250358 > rasanj...@wso2.com > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
