This is an automated email from the ASF dual-hosted git repository.
bharathkk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/samza.git
The following commit(s) were added to refs/heads/master by this push:
new 02e15bd Fixed broken links in documentation
new ad64622 Merge pull request #1143 from ferozmbasheer/samza-fixdocs
02e15bd is described below
commit 02e15bdd9259e7c555694bc2f609c8c7d9ac7a80
Author: Feroz Basheer <[email protected]>
AuthorDate: Tue Aug 20 21:59:23 2019 -0700
Fixed broken links in documentation
This fixes two broken links in deployment model page (to YARN and
standalone deployment pages).
---
docs/learn/documentation/versioned/deployment/deployment-model.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/learn/documentation/versioned/deployment/deployment-model.md
b/docs/learn/documentation/versioned/deployment/deployment-model.md
index ba100da..9a39cb8 100644
--- a/docs/learn/documentation/versioned/deployment/deployment-model.md
+++ b/docs/learn/documentation/versioned/deployment/deployment-model.md
@@ -23,13 +23,13 @@ title: Deployment options
A unique thing about Samza is that it provides multiple ways to run your
applications. Each deployment model comes with its own benefits, so you have
flexibility in choosing whichever fits your needs. Since Samza supports “Write
Once, Run Anywhere”, your application logic does not change depending on where
you deploy it.
### Running Samza on YARN
-Samza integrates with [Apache
YARN](learn/documentation/{{site.version}}/deployment/yarn.html) for running
stream-processing as a managed service. We leverage YARN for isolation,
multi-tenancy, resource-management and deployment for your applications. In
this mode, you write your Samza application and submit it to be scheduled on a
YARN cluster. You also specify its resource requirement - the number of
containers needed, number of cores and memory required per-container. Samza
then works [...]
+Samza integrates with [Apache
YARN](/learn/documentation/{{site.version}}/deployment/yarn.html) for running
stream-processing as a managed service. We leverage YARN for isolation,
multi-tenancy, resource-management and deployment for your applications. In
this mode, you write your Samza application and submit it to be scheduled on a
YARN cluster. You also specify its resource requirement - the number of
containers needed, number of cores and memory required per-container. Samza
then work [...]
When multiple applications share the same YARN cluster, they need to be
isolated from each other. For this purpose, Samza works with YARN to enforce
cpu and memory limits. Any application that uses more than its requested share
of memory or cpu is automatically terminated - thereby, allowing multi-tenancy.
Just like you would for any YARN-based application, you can use YARN's [web
UI](/learn/documentation/{{site.version}}/deployment/yarn.html#application-master-ui)
to manage your Samza j [...]
### Running Samza in standalone mode
-Often you want to embed and integrate Samza as a component within a larger
application. To enable this, Samza supports a [standalone
mode](learn/documentation/{{site.version}}/deployment/standalone.html) of
deployment allowing greater control over your application's life-cycle. In this
model, Samza can be used just like any library you import within your Java
application. This is identical to using a [high-level Kafka
consumer](https://kafka.apache.org/) to process your streams.
+Often you want to embed and integrate Samza as a component within a larger
application. To enable this, Samza supports a [standalone
mode](/learn/documentation/{{site.version}}/deployment/standalone.html) of
deployment allowing greater control over your application's life-cycle. In this
model, Samza can be used just like any library you import within your Java
application. This is identical to using a [high-level Kafka
consumer](https://kafka.apache.org/) to process your streams.
You can increase your application's capacity by spinning up multiple
instances. These instances will then dynamically coordinate with each other and
distribute work among themselves. If an instance fails for some reason, the
tasks running on it will be re-assigned to the remaining ones. By default,
Samza uses [Zookeeper](https://zookeeper.apache.org/) for coordination across
individual instances. The coordination logic by itself is pluggable and hence,
can integrate with other frameworks.
