On Wed, Nov 5, 2014 at 10:37 AM, Udara Liyanage <[email protected]> wrote:
> Hi Imesh, > > When new MySQL started, it publish its details to the metadata which will > overwrite the existing values. > > In terminate-all, terminate-dependent this won't be an issue since PHP > instance also get killed. So the idea I got is, it is the responsibility of > the application deployer to mark it terminate-dependent in such a case. > > IMO, yes > On Wed, Nov 5, 2014 at 12:01 AM, Imesh Gunaratne <[email protected]> wrote: > >> On Tue, Nov 4, 2014 at 11:43 PM, Udara Liyanage <[email protected]> wrote: >> >>> Hi Lakmal, >>> >>> What I meant by restarted is starting another instance when an existing >>> instance is terminated for some reason. Application monitor respin another >>> instance when a dependency is terminated. However the data fetched from >>> metadata service (by PHP instance) is outdated. >>> >>> As I can recall we discussed this issue before, the meta-data service >> can keep the member id against each record and invalidate the record if the >> member is terminated. Then the next member comes in can add a new record. >> >>> @Imesh there might be cases where LB is not included in an application. >>> In PHP and MySQL scenario it may be better to go via LB, but in generic it >>> is ok to go without an LB >>> >> Agree, there can be situations where we only need one instance of a >> service. >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > > Udara Liyanage > Software Engineer > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > web: http://udaraliyanage.wordpress.com > phone: +94 71 443 6897 > -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
