Skip to content
mlimotte edited this page Feb 20, 2013 · 3 revisions

Assuming install is done and $LEMUR_HOME/bin is in your PATH. You run lemur like this:

lemur <command> <jobdef-file> [options] [remaining]

lemur help                    - display this help text
lemur run ./jobdef.clj        - Run a job on EMR
lemur dry-run ./jobdef.clj    - Dry-run, i.e. just print out what would be done
lemur start ./jobdef.clj      - Start an EMR cluster, but don't run the steps (jobs)
lemur local ./jobdef.clj      - Run the job using local hadoop (e.g. standalone mode)
lemur submit ./jobdef.clj --jobflow j-123456789   - Submit steps to a running jobflow (cluster)

lemur display-types      - Display the instance-types with basic stats and exit
lemur spot-price-history - Display the spot price history for the last day and exit

Examples:
lemur run path/to/your-jobdef.clj --foo --bar 1
lemur start src/main/clj/lemur/sample-jobdef.clj

bin/lemur is sensitive to a few environment variables:

  • export LEMUR_EXTRA_CLASSPATH=...

Comma separated list of classpaths that should be added before your jobdef runs

  • export LEMUR_AWS_ACCESS_KEY=...
  • export LEMUR_AWS_SECRET_KEY=...

These two are another way of setting your AWS credentials. If they are not set, lemur will try to find them according to the rules: https://github.com/TheClimateCorporation/lemur#aws-credentials

Clone this wiki locally