Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-29084

Stop Processing when Failure Threshold is Reached

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • Neo.next
    • 5.5.0
    • eventing
    • None

    Description

      A Function should stop processing if 'x' failures are reached over a duration of 'y' seconds. Both 'x' and 'y' should be Function Level Configurations.

      On ReDeployment of the Function: it should start from the mutation that last errored.

      The rational for not reprocessing from the first mutation that errored is:

      • very difficult to find out which was the seq num that errored prior to 'y' seconds. (Implementation Detail: It is presumed that there is a function level counter that keeps incrementing when errors are stumbled upon(a la sliding window operator) and worker thread always checks/looksup when an error is encountered; based on which further processing is stopped.)
      • user can always look at the Function log for all the failed executions and reprocess them(in a different process/application) before commencing redeployment.

       

       

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              srinivasan.raman Srinivasan Raman
              venkatraman.subramanian Venkatraman Subramanian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty