Hi All, Public jira for this is [1], and documentation jira is [2]
[1] - https://wso2.org/jira/browse/ESBJAVA-4677 [2] - https://wso2.org/jira/browse/DOCUMENTATION-3554 Thanks, On Mon, Jul 4, 2016 at 12:04 PM, Rajith Vitharana <[email protected]> wrote: > Hi All, > > This is done as mentioned in previous mail with git pull [1], [2], > currently we just identify clustering pattern as *not* "WorkerManager" > for ESB task purposes, hence may need to come up with other possible > pattern names in future. > > [1] - https://github.com/wso2/carbon-mediation/pull/652 > <https://github.com/wso2/carbon-mediation/pull/652/files> > [2] - https://github.com/wso2/product-esb/pull/551 > > Thanks, > > On Fri, Jul 1, 2016 at 7:43 AM, Isuru Udana <[email protected]> wrote: > >> Hi All, >> >> In ESB 4.9.0, we introduced coordination for following features >> - Scheduled Tasks >> - Inbound Endpoints >> - Message Processors >> >> In all these features coordination is implemented tightly coupling to the >> worker-manager deployment pattern. >> >> But we have the requirement to support coordination for clusters which is >> not following the worker-manager deployment pattern. >> >> Currently we are executing a task in a node by looking at following logic. >> >> IF clustered == False OR worker-node == True >> execute = true >> ELSE >> execute = false >> >> So if a node belongs to a cluster, it must be a worker node. We identify >> the worker node by looking at the -DworkerNode=true argument. >> Ideally we should identify the manager node and stop executing the task >> for that, but unfortunately there is no way to do that. >> >> So to support coordination for clusters which are not clustered in worker >> manager pattern, we need to identify the clustering pattern. >> >> So we thought of introducing a new parameter for the clustering >> configuration in axis2.xml. >> >> <parameter name="clusteringPattern">WorkerManager</parameter> >> >> We had an offline discussion on this with Azeez and Sagara as well, it >> seems like this is the best possible way we can handle this for the moment. >> >> Thanks, >> IsuruU >> >> -- >> *Isuru Udana* >> Technical Lead >> WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 3791887 >> blog: http://mytecheye.blogspot.com/ >> > > > > -- > Rajith Vitharana > > Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94715883223 > Blog : http://lankavitharana.blogspot.com/ > -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
