Hi all, Thank you for the information. I read the thread Lahiru mentioned and noticed three basic fault types are handled. Looks like everything is covered :)
What I would like to suggest is a way to customize this "Application process is terminated" fault type identification. Currently, cartridge agent will only check whether given ports in the payload are open. But there could be various scenarios where port is open does not necessarily translate to application is up and running as expected. Just a suggestion though. Thanks. On Wed, May 21, 2014 at 2:03 PM, Lahiru Sandaruwan <lahi...@wso2.com> wrote: > Following thread has some more information, > > "Fault handling scenarios for Stratos cartridge instances" > > > On Wed, May 21, 2014 at 2:02 PM, Lahiru Sandaruwan <lahi...@wso2.com> wrote: >> >> Looks like an information needs in docs, if we do not have already. >> >> We can have all the fault handling scenarios documented. >> >> >> On Wed, May 21, 2014 at 1:44 PM, Nirmal Fernando <nirmal070...@gmail.com> >> wrote: >>> >>> Yes, we already have such a mechanism, using CEP window processors. >>> >>> >>> On Wed, May 21, 2014 at 1:23 PM, Akila Ravihansa Perera >>> <raviha...@wso2.com> wrote: >>>> >>>> Hi, >>>> >>>> Currently, Stratos cartridge agent only publishes health stats related >>>> to that instance's system condition. IMO, there should be a way to >>>> identify whether the deployed application in cartridge instance is >>>> functioning properly. And it should ideally check this periodically >>>> (like a cron task). >>>> >>>> How about we introduce a new cartridge-agent extension to monitor >>>> application status? We run a shell script (can be customized by user) >>>> at a "monitor application" extension point periodically and depending >>>> on the exit code of the shell script agent will identify whether the >>>> deployed application is functioning properly. >>>> >>>> If the application is not functioning as expected, agent will publish >>>> a "Maintenance Mode" event. It will prevent LB members from forwarding >>>> requests to the instance. Ideally, this instance should get re-spawned >>>> by AS. >>>> >>>> This is merely a suggestion. Please add your comments. >>>> >>>> Thanks >>>> >>>> PS - I'm not aware of any mechanism already in place to check >>>> application condition. Please ignore this if such mechanism is already >>>> there. >>>> >>>> -- >>>> Akila Ravihansa Perera >>>> Software Engineer >>>> WSO2 Inc. >>>> http://wso2.com >>>> >>>> Phone: +94 77 64 154 38 >>>> Blog: http://ravihansa3000.blogspot.com >>> >>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Committer and PPMC member, Apache Stratos(incubating), >> Senior Software Engineer, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> email: lahi...@wso2.com cell: (+94) 773 325 954 >> blog: http://lahiruwrites.blogspot.com/ >> twitter: http://twitter.com/lahirus >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> > > > > -- > -- > Lahiru Sandaruwan > Committer and PPMC member, Apache Stratos(incubating), > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: lahi...@wso2.com cell: (+94) 773 325 954 > blog: http://lahiruwrites.blogspot.com/ > twitter: http://twitter.com/lahirus > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > -- Akila Ravihansa Perera Software Engineer WSO2 Inc. http://wso2.com Phone: +94 77 64 154 38 Blog: http://ravihansa3000.blogspot.com
