Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
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
- links to
