Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-1769

AppRunner#Status should not throw exceptions

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The first step in computing the status of a StreamApplication is to run the ExecutionPlanner. Since the planner is run prior to everything else, any user-level misconfiguration that can cause the planner to fail will also cause AppRunner#status to fail.

      To make the computing of AppRunner#status more robust, we should not rely on the entire ExecutionPlan. Instead, a short-term alternative might be to directly query the cluster-manager by providing the app-name and app-id. The YARNJob class implements a lot of this logic - So, should offer us good leverage here.

      For the long-term, it would be preferrable to rely on the MetadataStore abstraction in Samza to store history about runs of an application.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jagadish1989@gmail.com Jagadish
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: