keith-turner commented on a change in pull request #903: Fluo 897
URL: https://github.com/apache/fluo/pull/903#discussion_r131735469
##########
File path: docs/applications.md
##########
@@ -147,6 +128,102 @@ To create an observer, follow these steps:
are used by transactions to know when to trigger observers.
6. Start your Fluo instance so that your Fluo workers load the new observer.
+## Initialize Fluo application
+
+Below is an overview of what initialization does and some of the key
properties it uses.
+
+ * **Initialize ZooKeeper** : Each application has its own area in ZooKeeper
that is used for application configuration, Oracle state, and worker
coordination. All properties, except `fluo.connections.*`, are copied into
ZooKeeper. For example, if `fluo.worker.num.threads=128` was set, then when a
worker process starts it will read this from ZooKeeper.
+ * **Copy Observer jars to DFS** : Fluo workers processes need the jars
containing observers. These are provided in one of the following ways.
+ * Set the property `fluo.observer.init.dir` to a local directory containing
observer jars. The jars in this directory are copied to DFS under
`<fluo.dfs.root>/<app name>`. When a worker is started, the jars are pulled
from DFS and added to its classpath.
+ * Set the property `fluo.observer.jars.url` to a directory in DFS
containing observer jars. No copying is done. When a worker is started, the
jars are pulled from this location and added to its classpath.
+ * Do not set any of the properties above and have the mechanism that starts
the worker process add the needed jars to the classpath.
+ * **Create Accumulo table** : Each Fluo application creates and configures an
Accumulo table. The `fluo.accumulo.*` properties determine which Accumulo
instance is used. For performance reasons, Fluo runs its own code in Accumulo
tablet servers. Fluo attempts to copy Fluo jars into DFS and configure Accumulo
to use them. Fluo first checks the property `fluo.accumulo.jars` and if set,
copies the jars listed there. If that property is not set, then Fluo looks on
the classpath to find jars. Jars are copied to a location under
`<fluo.dfs.root>/<app name>`.
+
+Below are the steps to initialize an appliaction from the command line. It is
also possible to initialize an appliaction using Fluo's Java API.
Review comment:
fixed that, thanks
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
