[
https://issues.apache.org/jira/browse/SAMZA-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Bircakovic updated SAMZA-710:
----------------------------------------
Attachment: SAMZA-710.1.patch
Thank you, [Yan
Fang|https://issues.apache.org/jira/secure/ViewProfile.jspa?name=closeuris].
Here is my new patch.
> 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
> Assignee: Aleksandar Bircakovic
> Attachments: SAMZA-710.0.patch, SAMZA-710.1.patch
>
>
> [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)
