Hi All, With the requirement to remove Hazelcast from task scheduling related implementation in ESB/EI clusters, due to possible issues in partition scenarios, it was decided to introduce an alternative to Hazelcast in ntask [1]. Currently ntask uses Hazelcast for coordinator election (where the oldest member is elected as the coordinator) and it is this coordinator that handles rescheduling of tasks (fail-over). ntask also uses the Hazelcast distributed executor service (IExecutorService) with task scheduling calls, to schedule tasks on specific members.
Currently ntask already uses Quartz to schedule the tasks, but fail-over is handled explicitly by ntask. Scheduling related calls are executed on specific members via the distributed executor service by ntask. We are currently working on introducing Quartz's own clustering features which provide the required fail-over and load balancing functionality by coordinating via a database [2]. Please find attached a summary of the functionality/capabilities provided by Quartz clustering (summarizing [2]). With the introduction of Quartz's own clustering features, the ClusterGroupCommunicator in ntask will not be needed for task scheduling since the identification of nodes that have left and and rescheduling of tasks that were being executed by them will be handled by Quartz. The other task scheduling related calls such as pausing and resuming will also be handled by Quartz and thus would not require identification of the particular member executing the task and then executing the relevant call by ntask. [1] "Updated Invitation: RDBMS based Coordinator Election for EI/ESB - Design Review @ Tue Aug 22, 2017 4pm - 5pm (Maryam Ziyad)" [2] http://www.quartz-scheduler.org/documentation/quartz-2.x/configuration/ConfigJDBCJobStoreClustering.html Feedback would be appreciated. Thank you, Maryam -- *Maryam Ziyad Mohamed* Software Engineer | WSO2 [image: http://wso2.com/signature] <http://wso2.com/signature>
ntask - Introducing Quartz Clustering Features.pdf
Description: Adobe PDF document
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
