[jira] [Created] (SAMZA-710) Update WebServlet and RestServlet to read coordinatorStream information

["Yan Fang (JIRA)" <ji...@apache.org>]

Yan Fang created SAMZA-710:
------------------------------

             Summary: Update WebServlet and RestServlet to read coordinatorStream information
                 Key: SAMZA-710
                 URL: https://issues.apache.org/jira/browse/SAMZA-710
             Project: Samza
          Issue Type: Improvement
            Reporter: Yan Fang


[REST API|https://github.com/apache/samza/blob/master/samza-yarn/src/main/scala/org/apache/samza/webapp/ApplicationMasterRestServlet.scala] and the [dashboard|https://github.com/apache/samza/blob/master/samza-yarn/src/main/scala/org/apache/samza/webapp/ApplicationMasterWebServlet.scala] only read the static config information and the Yarn [State|https://github.com/apache/samza/blob/master/samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterState.scala]. This is not sufficient for future use cases: dynamic change config, expose jmx to the dashboard (SAMZA-670), show latest checkpoint in the dashboard, etc.

I think having both servlets read the coordinatorStream to get the latest jobModel is a promising way to solve above use cases. The solution should be similar to [JobServlet|https://github.com/apache/samza/blob/master/samza-core/src/main/scala/org/apache/samza/coordinator/server/JobServlet.scala] and [ServletBase|https://github.com/apache/samza/blob/master/samza-core/src/main/scala/org/apache/samza/coordinator/server/ServletBase.scala], where the servlet gets latest jobModel every time it receives a http request. Is it a little overkill?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)