Hi all, Lets begin by what we are trying to acheive. We need a simple solution to reduce the noise in the social wall, because it is not user friendly to receive 3 deployment messages if the app is deployed on 3 servers in the same cluster (ideally in our cloud we should do tenant partition properly for free users so that this won't happen). We are NOT trying to detect and notify failures. What we need a is to reduce noise in the wall. Hence I am +1 for the proposed simple solution.
If we want monitoring system we need to design it properly and do it more comprehensively. thanks, dimuthu On Mon, Jul 21, 2014 at 6:44 PM, Anuruddha Premalal <[email protected]> wrote: > Hi Amila, > > Yes topology will identify both and idea is to select a node with the > highest IP. > > > On Mon, Jul 21, 2014 at 5:53 PM, Amila Maha Arachchi <[email protected]> > wrote: > >> Hi Anuruddha, >> >> I have a question on this. If there are two application servers running >> in an AS cluster, isn't the topology identify both of them as active. If >> so, do you go for the highest IP? >> >> >> On Mon, Jul 21, 2014 at 5:28 PM, Anuruddha Premalal <[email protected]> >> wrote: >> >>> Hi, >>> >>> *Problem:* >>> >>> In the current appfactory setup all the application containers (AS) >>> notifies on application life cycle events (deployment, undeployment); this >>> is because the deployment event listeners directly send messages to >>> appfactory . This approach works well for a single node deployment . But it >>> will cause unwanted noise (which will ultimately be several copies of the >>> same message on the notification wall) in a clustered environment, also >>> this will cause unwanted traffic towards appfactory. So it is important to >>> limit notifications from the container level. >>> >>> *Solution:* >>> >>> Requirement is to send notifications only from a single appserver node >>> in the cluster. >>> >>> For this we have to choose a single candidate from the cluster, and make >>> him as the notifier node. >>> >>> Candidate selection method: >>> >>> This can be achieved using Stratos topology information. Topology(which >>> is published every 60secs) have information about currently active cluster >>> nodes. >>> >>> Application notifiers will subscribe to this topology topic and choose >>> to be the notifier based on the following criteria. >>> >>> 1.) If the topology contains the IP of the node. >>> Note : This is important because there might be cases where IP is >>> not in the topology but the instance is active. >>> >>> 2.) If the IP is the highest IP in the available topology. >>> >>> >>> Related Jira : https://wso2.org/jira/browse/APPFAC-2271 >>> >>> >>> Regards, >>> >>> -- >>> *Anuruddha Premalal* >>> Software Eng. | WSO2 Inc. >>> Mobile : +94710461070 >>> Web site : www.regilandvalley.com >>> >>> "Advances of technology should not leave behind the developing world" >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Anuruddha Premalal* > Software Eng. | WSO2 Inc. > Mobile : +94710461070 > Web site : www.regilandvalley.com > > "Advances of technology should not leave behind the developing world" > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dimuthu Leelarathne Architect & Product Lead of App Factory WSO2, Inc. (http://wso2.com) email: [email protected] Mobile : 0773661935 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
