You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2015/02/11 18:23:11 UTC

[jira] [Created] (SAMZA-558) Write a samza-standalone UI proxy

Chris Riccomini created SAMZA-558:
-------------------------------------

             Summary: Write a samza-standalone UI proxy
                 Key: SAMZA-558
                 URL: https://issues.apache.org/jira/browse/SAMZA-558
             Project: Samza
          Issue Type: Sub-task
          Components: container
    Affects Versions: 0.9.0
            Reporter: Chris Riccomini


It would be nice to have a central UI for samza-standalone jobs. This UI would serve several purposes:

# Act as a proxy to allow developers to view their JobCoordinator UIs and logs without having to poke a bunch of holes in production firewalls.
# Act as a router to point developers to the current location of their JobCoordinator's UI, which may bounce from host to host during fail-overs.
# Serve as a central point to find all currently-executing standalone jobs.

The YARN AM is currently what serves UI. The JobCoordinator has only a REST HTTP server, which serves the job model and configs for the job. Between the ZK data and the JobCoordinator's REST interface, this should be enough information for the standalone UI to construct the containers, task groups, and configs sections that the YARN UI displays.

The look and feel should appear the same as the YARN AM UI's look and feel.



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