Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
194 lines (142 sloc) 7.67 KB

Installing for Developers

Step 1: Build Myriad


  • Linux/Unix/Mac OS X
  • JDK 7
  • gradle
    • Gradle installation is required to build Myriad from a source release download
    • If building Myriad from the project's git clone, gradle installation is not required

Installing the gradle wrapper

These instructions apply to source release downloads only. If Myriad sources are checked out from the git repository, the gradle wrapper script will already be available.

Myriad's source release tarball does not include gradle wrapper script. So you'll need to:

  • Install gradle:
    • Please follow the instructions on gradle's website to install gradle. We tested Myriad with gradle 2.9.
  • Generate the gradle wrapper script:
    • Once gradle is installed, execute gradle wrapper command from the $PROJECT_ROOT of the Myriad project. This generates a $PROJECT_ROOT/gradlew script, and also places a supporting jar at $PROJECT_ROOT/gradle/wrapper/gradle-wrapper.jar.

Building the binaries

Ensure $PROJECT_ROOT/gradlew script is available. Run the following command from $PROJECT_ROOT to build Myriad (both Scheduler and Executor components):

./gradlew build

At this point the jars will be located in the following directories:

# scheduler jars

# executor jar

Building Myriad Scheduler Only

To build only the Scheduler, from $PROJECT_HOME, run:

./gradlew :myriad-scheduler:build

Building Myriad Executor Only

To build only the Executor, from $PROJECT_HOME, run:

./gradlew :myriad-executor:build

Step 2: Deploy the Myriad Binaries

To deploy Myriad Scheduler and Executor Binaries:

  1. Copy the Myriad Scheduler jar and it's dependencies from the $PROJECT_HOME/myriad-scheduler/build/libs/ directory to the $YARN_HOME/share/hadoop/yarn/lib/ directory on all nodes in your cluster.
  2. Copy the Myriad Executor myriad-executor-xxx.jar file from the $PROJECT_HOME/myriad-executor/build/libs/ directory to each mesos slave's $YARN_HOME/share/hadoop/yarn/lib/ directory.
  3. Copy the myriad-config-default.yml file from $PROJECT_HOME/myriad-scheduler/build/src/main/resources/ directory to the $YARN_HOME/etc/hadoop directory.

For example:

cp myriad-scheduler/build/libs/*.jar /opt/hadoop-2.7.0/share/hadoop/yarn/lib/
cp myriad-executor/build/libs/myriad-executor-0.1.0.jar /opt/hadoop-2.7.0/share/hadoop/yarn/lib/
cp myriad-scheduler/build/resources/main/myriad-config-default.yml /opt/hadoop-2.7.0/etc/hadoop/

NOTE: For advanced users, you can also copy myriad-executor-xxx.jar to any other directory on a slave filesystem or it can be copied to HDFS as well. In either case, you need to update the executor's path property in the myriad-config-default.yml file and prepend the path with either file:// or hdfs://, as appropriate.

Step 3: Configure the Myriad Defaults

As a minimum, the following Myriad configuration parameters must be set:

  • mesosMaster
  • zkServers

Enabling Cgroups involves modifying the yarn-site.xml and myriad-config-default.yml files. If you plan on using Cgroups, you could set that property at this time. See Configuring Cgroup for more information.

NOTE: By copying the myriad-config-default.yml file to the /etc/hadoop directory, you can make changes to the configuration file without having to rebuild Myriad. If you specify the Myriad configuration parameters before building Myriad, you must rebuild Myriad and redeploy the jar files. This is required because the myriad-config-default.yml file is embedded into the Myriad Scheduler jar.

Step 4: Configure YARN to Use Myriad

In order to run Myriad, the following YARN properties must be modified on each node in the cluster:

  • Edit the $YARN_HOME/etc/hadoop/ file and add the following:
export MESOS_NATIVE_JAVA_LIBRARY=/usr/local/lib/
  • Edit the $YARN_HOME/etc/hadoop/yarn-site.xml file and add the following:
<!--These options enable dynamic port assignment by mesos -->
<!-- Configure Myriad Scheduler here -->
    <description>One can configure other scehdulers as well from following list: org.apache.myriad.scheduler.yarn.MyriadCapacityScheduler, org.apache.myriad.scheduler.yarn.MyriadFifoScheduler</description>
  • Edit the $YARN_HOME/etc/hadoop/mapred-site.xml file and add the dynamic port assignment properties.

    1. On each node, change directory to $YARN_HOME/etc/hadoop.
    2. Copy mapred-site.xml.template to mapred-site.xml.
    3. Edit and add the following property to the mapred-site.xml file.
// Add following to $YARN_HOME/etc/hadoop/mapred-site.xml:
<!--This option enables dynamic port assignment by mesos -->

Starting the Resource Manager

Myriad Scheduler runs inside Resource Manager as a plugin. To start the Resource Manager:

./sbin/ start resourcemanager

Running Myriad Executor and Node Managers

Myriad Executor and Node Managers are launched automatically by Myriad Scheduler as a response to flexup and flex down behavior. See the Myriad Cluster API.

Setting up Editor/IDE Support

You are welcome to use any editor you like, however, many of the myriad developers use IntelliJ IDEA. The build process described below uses gradle. The build script is configured with the idea plugin to create an intellij project structure. This is accomplished with the following command:

./gradlew idea

# to open on a mac
open myriad.ipr

NOTE: If you are interested in using eclipse, there is a plugin for that. Either send in a pull request, or send a message on the dev mail list that you would make use of it.

Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
You can’t perform that action at this time.