You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by ya...@apache.org on 2015/07/16 02:13:18 UTC
samza git commit: SAMZA-734: removed redundant dashboard in
Application Master page
Repository: samza
Updated Branches:
refs/heads/master 3d1fd2171 -> 9709d9d46
SAMZA-734: removed redundant dashboard in Application Master page
Project: http://git-wip-us.apache.org/repos/asf/samza/repo
Commit: http://git-wip-us.apache.org/repos/asf/samza/commit/9709d9d4
Tree: http://git-wip-us.apache.org/repos/asf/samza/tree/9709d9d4
Diff: http://git-wip-us.apache.org/repos/asf/samza/diff/9709d9d4
Branch: refs/heads/master
Commit: 9709d9d4632cff6ad7ca34405f733311a9fd64a0
Parents: 3d1fd21
Author: Aleksandar Pejakovic <a....@levi9.com>
Authored: Wed Jul 15 17:12:40 2015 -0700
Committer: Yan Fang <ya...@gmail.com>
Committed: Wed Jul 15 17:12:40 2015 -0700
----------------------------------------------------------------------
.../versioned/jobs/configuration-table.html | 2 +-
.../documentation/versioned/yarn/application-master.md | 13 -------------
2 files changed, 1 insertion(+), 14 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/samza/blob/9709d9d4/docs/learn/documentation/versioned/jobs/configuration-table.html
----------------------------------------------------------------------
diff --git a/docs/learn/documentation/versioned/jobs/configuration-table.html b/docs/learn/documentation/versioned/jobs/configuration-table.html
index cd7ea8d..6aa7b91 100644
--- a/docs/learn/documentation/versioned/jobs/configuration-table.html
+++ b/docs/learn/documentation/versioned/jobs/configuration-table.html
@@ -122,7 +122,7 @@
<strong>Required:</strong> The <a href="job-runner.html">job factory</a> to use for running this job.
The value is a fully-qualified Java classname, which must implement
<a href="../api/javadocs/org/apache/samza/job/StreamJobFactory.html">StreamJobFactory</a>.
- Samza ships with two implementations:
+ Samza ships with three implementations:
<dl>
<dt><code>org.apache.samza.job.local.ThreadJobFactory</code></dt>
<dd>Runs your job on your local machine using threads. This is intended only for
http://git-wip-us.apache.org/repos/asf/samza/blob/9709d9d4/docs/learn/documentation/versioned/yarn/application-master.md
----------------------------------------------------------------------
diff --git a/docs/learn/documentation/versioned/yarn/application-master.md b/docs/learn/documentation/versioned/yarn/application-master.md
index d20aece..807f6f3 100644
--- a/docs/learn/documentation/versioned/yarn/application-master.md
+++ b/docs/learn/documentation/versioned/yarn/application-master.md
@@ -47,19 +47,6 @@ When the AM receives a reboot signal from YARN, it will throw a SamzaException.
If the AM, itself, fails, YARN will handle restarting the AM. When the AM is restarted, all containers that were running will be killed, and the AM will start from scratch. The same list of operations, shown above, will be executed. The AM will request new containers for its SamzaContainers, and proceed as though it has just started for the first time. YARN has a yarn.resourcemanager.am.max-retries configuration parameter that's defined in [yarn-site.xml](http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-common/yarn-default.xml). This configuration defaults to 1, which means that, by default, a single AM failure will cause your Samza job to stop running.
-### Dashboard
-
-Samza's ApplicationMaster comes with a dashboard to show useful information such as:
-
-1. Where containers are located.
-2. Links to logs.
-3. The Samza job's configuration.
-4. Container failure count.
-
-You can find this dashboard by going to your YARN grid's ResourceManager page (usually something like [http://localhost:8088/cluster](http://localhost:8088/cluster)), and clicking on the "ApplicationMaster" link of a running Samza job.
-
-<img src="/img/{{site.version}}/learn/documentation/yarn/samza-am-dashboard.png" alt="Screenshot of ApplicationMaster dashboard" class="diagram-large">
-
### Security
The Samza dashboard's HTTP access is currently un-secured, even when using YARN in secure-mode. This means that users with access to a YARN grid could port-scan a Samza ApplicationMaster's HTTP server, and open the dashboard in a browser to view its contents. Sensitive configuration can be viewed by anyone, in this way, and care should be taken. There are plans to secure Samza's ApplicationMaster using [Hadoop's security](http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.3.0/bk_installing_manually_book/content/rpm-chap14-2-3-1.html) features ([SPENAGO](http://en.wikipedia.org/wiki/SPNEGO)).