You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@falcon.apache.org by sr...@apache.org on 2014/12/01 04:00:27 UTC
incubator-falcon git commit: FALCON-734 Document when to use
Distributed Mode vs. Embedded Mode. Contributed by Ajay Yadav
Repository: incubator-falcon
Updated Branches:
refs/heads/master 97b5989a1 -> eafab696c
FALCON-734 Document when to use Distributed Mode vs. Embedded Mode. Contributed by Ajay Yadav
Project: http://git-wip-us.apache.org/repos/asf/incubator-falcon/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-falcon/commit/eafab696
Tree: http://git-wip-us.apache.org/repos/asf/incubator-falcon/tree/eafab696
Diff: http://git-wip-us.apache.org/repos/asf/incubator-falcon/diff/eafab696
Branch: refs/heads/master
Commit: eafab696c11b748b8495cb03755bbe5221b17db6
Parents: 97b5989
Author: srikanth.sundarrajan <sr...@apache.org>
Authored: Mon Dec 1 08:30:15 2014 +0530
Committer: srikanth.sundarrajan <sr...@apache.org>
Committed: Mon Dec 1 08:30:15 2014 +0530
----------------------------------------------------------------------
CHANGES.txt | 3 +++
docs/src/site/twiki/FalconDocumentation.twiki | 13 ++++++++++---
2 files changed, 13 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-falcon/blob/eafab696/CHANGES.txt
----------------------------------------------------------------------
diff --git a/CHANGES.txt b/CHANGES.txt
index ed2ff32..02c4e1d 100755
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -19,6 +19,9 @@ Trunk (Unreleased)
FALCON-805 Create store to store feed properties like name against
it's path (Ajay Yadav via Srikanth Sundarrajan)
+ FALCON-734 Document when to use Distributed Mode vs. Embedded Mode
+ (Ajay Yadav via Srikanth Sundarrajan)
+
OPTIMIZATIONS
FALCON-913 Change the default values of log clean up services
(Suhas vasu)
http://git-wip-us.apache.org/repos/asf/incubator-falcon/blob/eafab696/docs/src/site/twiki/FalconDocumentation.twiki
----------------------------------------------------------------------
diff --git a/docs/src/site/twiki/FalconDocumentation.twiki b/docs/src/site/twiki/FalconDocumentation.twiki
index c413338..71ea1d5 100644
--- a/docs/src/site/twiki/FalconDocumentation.twiki
+++ b/docs/src/site/twiki/FalconDocumentation.twiki
@@ -56,11 +56,18 @@ There are two basic components of Falcon set up. Falcon Prism and Falcon Server.
As the name suggests Falcon Prism splits the request it gets to the Falcon Servers. More details below:
---+++ Stand Alone Mode
-Stand alone mode is useful when the hadoop jobs and relevant data processing involves only one hadoop cluster. In this mode there is single Falcon server that contacts with oozie to schedule jobs on Hadoop. All the process / feed request like submit, schedule, suspend, kill are sent to this server only. For running in this mode one should use the falcon which has been built for standalone mode, or build using standalone option if using source code.
+Stand alone mode is useful when the hadoop jobs and relevant data processing involves only one hadoop cluster.
+In this mode there is a single Falcon server that contacts Oozie to schedule jobs on Hadoop.
+All the process/feed requests like submit, schedule, suspend, kill etc. are sent to this server.
+For running falcon in this mode one should use the falcon which has been built using standalone option.
---+++ Distributed Mode
-Distributed mode is the mode which you might me using most of the time. This is for organisations which have multiple instances of hadoop clusters, and multiple workflow schedulers to handle them. Here we have 2 components: Prism and Server. Both Prism and server have there own setup (runtime and startup properties) and there config locations.
-In this mode Prism acts as a contact point for Falcon servers. Below are the requests that can be sent to prism and server in this mode:
+Distributed mode is for multiple (colos) instances of hadoop clusters, and multiple workflow schedulers to handle them.
+In this mode falcon has 2 components: Prism and Server(s).
+Both Prism and servers have their own setup (runtime and startup properties) and their own config locations.
+In this mode Prism acts as a contact point for Falcon servers.
+While all commands are available through Prism, only read and instance api's are available through Server.
+Below are the requests that can be sent to each of these:
Prism: submit, schedule, submitAndSchedule, Suspend, Resume, Kill, instance management
Server: schedule, suspend, resume, instance management