Skip to content

Latest commit

 

History

History
128 lines (101 loc) · 5.16 KB

myriad-dev.md

File metadata and controls

128 lines (101 loc) · 5.16 KB
Raw

Myriad development

Build instructions

System requirements:

  • JDK 1.7+
  • Gradle
  • Hadoop 2.5.0

Myriad requires two components to be built:

  • Myriad Scheduler - This component plugs into Resource Manager process and negotiates resources from Mesos. It is responsible to launch Node Manager processes via Mesos.
  • Myriad Executor - This component implements Mesos Executor interface. It is launched by Myriad Scheduler via Mesos and runs as a separate process on each mesos-slave. Myriad Executor is responsible for launching Node Manager process as a Mesos Task.

Building Myriad Scheduler

Before building Myriad Scheduler, please modify myriad-config-default.yml with appropriate configuration properties (Please read Myriad Configuration Properties). This is needed because currently myriad-config-default.yml will be embedded into Myriad Scheduler jar.

To build Myriad Scheduler run:

./gradlew build

This will build myriad-x.x.x.jar and download the runtime jars and place them inside PROJECT_HOME/build/libs/ directory.

Building Myriad Executor

To build self-contained executor jar, run:

./gradlew capsuleExecutor

This will build myriad-executor-x.x.x.jar and place it inside PROJECT_HOME/build/libs/ directory.

Deploying Myriad Scheduler

To deploy Myriad Scheduler, please follow the below steps:

  1. Build Myriad Scheduler
  2. Copy all jars under PROJECT_HOME/build/libs/ directory, to YARN ResourceManager's classpath. For ex: Copy all jars to $YARN_HOME/share/hadoop/yarn/lib/

Deploying Myriad Executor

To deploy Myriad Executor, please follow the below steps:

  1. Build Myriad Executor
  2. Copy myriad-executor-xxx.jar from PROJECT_HOME/build/libs/ to each mesos slave's /usr/local/libexec/mesos directory.

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

Running Myriad Scheduler

To run Myriad Scheduler, you need to follow following steps:

  • Add MESOS_NATIVE_JAVA_LIBRARY environment variable to ResourceManager's environment variables, for ex: Add following to $YARN_HOME/etc/hadoop/hadoop-env.sh:
export MESOS_NATIVE_JAVA_LIBRARY=/usr/local/lib/libmesos.so
  • Add following to $YARN_HOME/etc/hadoop/yarn-site.xml:
<property>
    <name>yarn.nodemanager.resource.cpu-vcores</name>
    <value>${nodemanager.resource.cpu-vcores}</value>
</property>
<property>
    <name>yarn.nodemanager.resource.memory-mb</name>
    <value>${nodemanager.resource.memory-mb}</value>
</property>

<!-- Configure Myriad Scheduler here -->
<property>
    <name>yarn.resourcemanager.scheduler.class</name>
    <value>com.ebay.myriad.scheduler.yarn.MyriadFairScheduler</value>
    <description>One can configure other scehdulers as well from following list: com.ebay.myriad.scheduler.yarn.MyriadCapacityScheduler, com.ebay.myriad.scheduler.yarn.MyriadFifoScheduler</description>
</property>

Optional: If you would like to enable cgroups, please add following to yarn-site.xml:

<!-- Cgroups specific configuration -->
<property>
    <description>who will execute(launch) the containers.</description>
    <name>yarn.nodemanager.container-executor.class</name>
    <value>${yarn.nodemanager.container-executor.class}</value>
</property>
<property>
    <description>The class which should help the LCE handle resources.</description>
    <name>yarn.nodemanager.linux-container-executor.resources-handler.class</name>
    <value>${yarn.nodemanager.linux-container-executor.resources-handler.class}</value>
</property>
<property>
    <name>yarn.nodemanager.linux-container-executor.cgroups.hierarchy</name>
    <value>${yarn.nodemanager.linux-container-executor.cgroups.hierarchy}</value>
</property>
<property>
    <name>yarn.nodemanager.linux-container-executor.cgroups.mount</name>
    <value>${yarn.nodemanager.linux-container-executor.cgroups.mount}</value>
</property>
<property>
    <name>yarn.nodemanager.linux-container-executor.cgroups.mount-path</name>
    <value>${yarn.nodemanager.linux-container-executor.cgroups.mount-path}</value>
</property>
<property>
    <name>yarn.nodemanager.linux-container-executor.group</name>
    <value>${yarn.nodemanager.linux-container-executor.group}</value>
</property>
<property>
    <name>yarn.nodemanager.linux-container-executor.path</name>
    <value>${yarn.home}/bin/container-executor</value>
</property>

And, following to $YARN_HOME/etc/hadoop/myriad-config-default.yml:

...
nodemanager:
    cgroups: true
...
  • Start Resource Manager. Myriad Scheduler will run inside Resource Manager as a plugin.
yarn-daemon.sh start resourcemanager

Running Myriad Executor / Node Managers

Myriad Executor and Node Managers are launched automatically by Myriad Scheduler as a response to flexup REST API.