Fluo 1.2.0 documentation >> Administration >> Initialize Application
Before a Fluo Application can run, it must be initialized. Below is an overview of what initialization does and some of the properties that may be set for initialization.
fluo.connections.*, are copied into ZooKeeper. For example, if
fluo.worker.num.threads=128was set, then when a worker process starts it will read this from ZooKeeper.
fluo.observer.init.dirto 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.
fluo.observer.jars.urlto 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.
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.jarsand 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
Below are the steps to initialize an application from the command line. It is also possible to initialize an application using Fluo’s Java API.
Create a copy of fluo-app.properties for your Fluo application.
cp $FLUO_HOME/conf/fluo-app.properties /path/to/myapp/fluo-app.properties
Edit your copy of fluo-app.properties and make sure to set the following:
When configuring the observer section of fluo-app.properties, you can configure your instance for the phrasecount application if you have not created your own application. See the phrasecount example for instructions. You can also choose not to configure any observers but your workers will be idle when started.
Run the command below to initialize your Fluo application. Change
myapp to your application name:
fluo init myapp /path/to/myapp/fluo-app.properties
A Fluo application only needs to be initialized once. After initialization, the Fluo application name is used to start/stop the application and scan the Fluo table.
fluo list which connects to Fluo and lists applications to verify initialization.
fluo config myapp to see what configuration is stored in ZooKeeper.
Run your Fluo application using one of the methods below:
Also, learn how to manage Fluo applications.