We discussed the existing logic in which we do not schedule a task on a manager node, and, due to this the tenants do not receive the same task definition although the registry is shared among them. To avoid this, we will write a new resolver that executes tasks only on worker nodes, and update the logic to schedule even on manager nodes. That way we can make sure that a task will be deployed in the manager node but not run.
Thanks, Ishan. On Wed, Feb 18, 2015 at 2:53 PM, Kasun Indrasiri <[email protected]> wrote: > We had a design review on this. Ishan is working on task resolver based > solution for this. > > Malaka/Ishan please share the meeting notes. > > On Tue, Feb 17, 2015 at 9:05 PM, Malaka Silva <[email protected]> wrote: > >> Hi Kasun, >> >> This is done at Task Adapter level. >> >> Task manager will invoke the task weather the tenant is loaded or not. >> However we require the tenant to be loaded to get the configs. Tenant >> loading is done inside task adapter [1]. >> >> However the case Maheeka mentioned, since the artifacts are not >> getting deployed it'll not register the task. >> >> [1] >> https://github.com/wso2/carbon-mediation/blob/master/components/mediation-ntask/src/main/java/org/wso2/carbon/mediation/ntask/NTaskAdapter.java >> >> On Tue, Feb 17, 2015 at 10:52 AM, Kasun Indrasiri <[email protected]> wrote: >> >>> @Malaka AFAIR, we have address this requirement during the initial >>> implementation. So the main concerns are : >>> >>> - How did we initially verify the functionality in a W/M setup for a >>> tenant? (When we initially create a tenant and then deploy an inbound.. did >>> that work?) >>> - How does we keep tenant loaded all the time if we have polling inbound >>> (based on ntasks) running. >>> >>> >>> On Tue, Feb 17, 2015 at 10:46 AM, Maheeka Jayasuriya <[email protected]> >>> wrote: >>> >>>> Hi Malaka, >>>> >>>> In a cluster setup, if a tenant is created, the artifacts related to >>>> tenant does not get deployed to worker nodes, unless the tenant is loaded >>>> manually in each of them. >>>> >>>> Is this scenario applicable for inbound-endpoints? Or is there a >>>> different mechanism to make sure that tenants are loaded in worker nodes in >>>> a case of inbound-endpoints? >>>> >>>> Thanks, >>>> >>>> Maheeka Jayasuriya >>>> Software Engineer >>>> Mobile : +94777750661 >>>> >>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> > > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- Ishan Jayawardena Senior Software Engineer
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
