retry-later for deferring driver events

Idea ID 2790671

retry-later for deferring driver events

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
1 Comment
Absent Member.
Absent Member.
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
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.