You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a two node cluster, when we create scheduled tasks and inbound endpoints to consume messages from the Message Broker (MB), upon server startup, half of the tasks were scheduled on node1 (the coordinator) and the other half on node2 (the member). task_server_count as 2 as below mentioned.
When reviewing the WSO2_COORDINATION_DB, it seems tasks scheduled on node1 were present in the COORDINATED_TASK_TABLE. The tasks scheduled on node2 were missing from the database. As a result, the tasks scheduled on node2 were being pushed but never started on either node, leading to failures in task execution across the cluster.
Version
4.1.0.111
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered:
Description
In a two node cluster, when we create scheduled tasks and inbound endpoints to consume messages from the Message Broker (MB), upon server startup, half of the tasks were scheduled on node1 (the coordinator) and the other half on node2 (the member). task_server_count as 2 as below mentioned.
[task_handling]
resolver_class = "org.wso2.micro.integrator.ntask.coordination.task.resolver.RoundRobinResolver"
[[task_resolver]]
task_server_count = "2"
When reviewing the WSO2_COORDINATION_DB, it seems tasks scheduled on node1 were present in the COORDINATED_TASK_TABLE. The tasks scheduled on node2 were missing from the database. As a result, the tasks scheduled on node2 were being pushed but never started on either node, leading to failures in task execution across the cluster.
Version
4.1.0.111
Environment Details (with versions)
No response
The text was updated successfully, but these errors were encountered: