[jboss-jira] [JBoss JIRA] (JGRP-1557) SUPERVISOR: protocol to check conditions and perform corrective actions if needed
Bela Ban (JIRA)
jira-events at lists.jboss.org
Wed Jan 2 07:54:08 EST 2013
[ https://issues.jboss.org/browse/JGRP-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban resolved JGRP-1557.
----------------------------
Resolution: Done
> SUPERVISOR: protocol to check conditions and perform corrective actions if needed
> ---------------------------------------------------------------------------------
>
> Key: JGRP-1557
> URL: https://issues.jboss.org/browse/JGRP-1557
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> SUPERVISOR is a protocol anywhere in the stack that passes messages up and down by default; it doesn't take part in message processing.
> However, it handles events ADD_RULE / REMOVE_RULE, which adds/removes rules. A rule is a condition with a name, an interval and an (optional) action.
> When the interval for a condition has elapsed, it is triggered and (if true) it'll invoke the associated action. A condition can be triggered by an interval elapsed or perhaps also when a event is received (e.g. a view change).
> Example:
> - Condition: check if FD is present in the stack. If it is and fd.isMonitorRunning() == false and fd.getView().size() > 1, then call action fd.startFailureDetection() and log an error message.
> The error messages are stored in a bounded list, so the last N error messages can be retrieved, e.g. via probe.sh.
> A rule should be able to be invoked manually, e.g. via probe.
> SUPERVISOR could be configured with a file which lists the rules to be created (class name, interval, description etc) at startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list