I have 3 node sensu go cluster and having 100+ checks where some of the checks are executing with proxyclient roundrobin attributes.
The roundrobin checks stops executing after executing for certain period. This scheduler issue making sensu unusuable.
Logs showing sending check request but check is not executing.
I created github issues but not getting any response. At least expecting response from sensu team.
The check definition
{
“api_version”:“core/v2”,
“type”:“Check”,
“metadata”:{
“namespace”:“default”,
“name”:“tech-mdm-ui-status”,
“labels”:{},
“annotations”:{
“sensu.io.json_attributes”:"{“type”:“standard”,“occurrences”:3,“refresh”:3600}",
“fatigue_check/occurrences”:“3”,
“fatigue_check/interval”:“3600”
}
},
“spec”:{
“command”:“bash /etc/sensu/plugins/mdm-ui-check.sh”,
“subscriptions”:[
“worker”
],
“publish”:true,
“round_robin”:true,
“interval”:60,
“handlers”:[
“alert_handler”,
“ops_alert_handler”,
“resolve_handler”,
“tester_handler”
],
“proxy_entity_name”:“proxyclient”,
“timeout”:50
}
}
Log says sending check request but does not get any event. This means only sending check request but execution is not happening. In such case log should through error for not executing the check.
If one of the sensu backend stops then checks aren’t automatically shifting to another sensu server.
All the roundrobin checks having issues. Checks without roundrobin works quite fine. I think there is serious issue with roundrobin checks
Need assistance for fixing the issues