If a driver returns the "retry" status level, the current event will be kept in the driver's queue and retried 30s later. Until the event is eventually processed to a "success" or "error" statuts, no other events will be processed.
If there is no requirement on a strict processing order of events, the driver should be able to postpone the processing of this event and continue with other events currently in its queue: If a policy returns a status with @level="retry-later", the engine should remove the event from the head of the queue and re-add it at the queue's tail position.
Optionally an @retry-not-before="yyyyMMddHHmmss.SSSZ" could be added to the status to indicate that is useless to retry the operation before that time. Default value for this option should be now+30s to avoid high utlization issues.
references:
https://forums.novell.com/showthread.php/484737-Force-Driver-into-Retry-State
https://secure-www.novell.com/rms/rmsTool?action=ReqActions.viewPropsPage&return=myReqs&reqId=84492
by: Norbert K. | over a year ago | Other
Comments
Also potentially add a retry count and let the customer policy determine next actions.
ie @retry-count=20, and customer can add a policy to potentially veto the event and send notification