Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-1494 Revisit of Client and Apis
  3. FALCON-1495

In instance status list, show all runs for instances when requested by user

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • trunk
    • ease, general
    • None

    Description

      Most of the times , when there are failures in the pipelines, retries run and the workflows might have got succeeded in sub sequential retry. But for end user to figure out why it has failed initially might be useful to understand for failures handling and SLA misses.

      As of now to figure out the same, its a tedious task to get such information by either going through oozie DB/logs or via the logs backed up in hdfs by the falcon postprocessing(which is 100% reliable as in few cases, falcon post processing might fail or for some reason if it couldn't back up the logs).

      In either case, Falcon should abstract the oozie client layer to be used by end user, and support all runs status to end user.

      Attachments

        1. FALCON-1495-v0.patch
          29 kB
          Narayan Periwal
        2. FALCON-1495-v1.patch
          31 kB
          Narayan Periwal
        3. FALCON-1495-v2.patch
          37 kB
          Narayan Periwal
        4. FALCON-1495-v3.patch
          44 kB
          Narayan Periwal
        5. FALCON-1495-v4.patch
          49 kB
          Narayan Periwal
        6. FALCON-1495-v5.patch
          50 kB
          Ajay Yadav

        Issue Links

          Activity

            People

              nperiwal Narayan Periwal
              sandeep.samudrala sandeep samudrala
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: