You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@fluo.apache.org by mw...@apache.org on 2018/08/01 16:09:02 UTC

[fluo-muchos] branch master updated: Fixes #229 - Create 'client' service (#230)

This is an automated email from the ASF dual-hosted git repository.

mwalch pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/fluo-muchos.git


The following commit(s) were added to refs/heads/master by this push:
     new 962cdd1  Fixes #229 - Create 'client' service (#230)
962cdd1 is described below

commit 962cdd11fe07723576be8141fa12a2b312979b3f
Author: Mike Walch <mw...@apache.org>
AuthorDate: Wed Aug 1 12:08:59 2018 -0400

    Fixes #229 - Create 'client' service (#230)
---
 README.md                 | 3 +++
 conf/muchos.props.example | 2 +-
 lib/muchos/config.py      | 4 ++--
 3 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 17aafef..d64b07c 100644
--- a/README.md
+++ b/README.md
@@ -98,6 +98,9 @@ be started on all workers nodes. The Mesos status page will be viewable at
 `http://<MESOS_MASTER_NODE>:5050/`. Marathon will also be started on this node and will be viewable
 at `http://<MESOS_MASTER_NODE>:8080/`.
 
+5. `client` - Used to specify a client node where no services are run but libraries are installed to
+run Accumulo/Hadoop clients.
+
 If you run the `muchos setup` command and a failure occurs, you can repeat the command until setup
 completes. Any work that was successfully completed will not be repeated. While some setup steps can
 take over a minute, use `ctrl-c` to stop setup if it hangs for a long time. Just remember to run
diff --git a/conf/muchos.props.example b/conf/muchos.props.example
index 666b1f9..64fc905 100644
--- a/conf/muchos.props.example
+++ b/conf/muchos.props.example
@@ -157,7 +157,7 @@ yarn_nm_mem_mb=16384
 # <Hostname> = <Service1>[,<Service2>,<Service3>]
 # Where:
 #   Hostname = Must be unique.  Will be used for hostname in EC2 or should match hostname on your own cluster
-#   Service = Service to run on node (possible values: zookeeper, namenode, resourcemanager, accumulomaster,
+#   Service = Service to run on node (possible values: zookeeper, namenode, resourcemanager, accumulomaster, client,
 #             mesosmaster, worker, fluo, metrics, spark). The following services are required: namenode, resourcemanager,
 #             accumulomaster, zookeeper & worker
 leader1 = namenode,resourcemanager,accumulomaster,zookeeper
diff --git a/lib/muchos/config.py b/lib/muchos/config.py
index 890abed..4d643b1 100644
--- a/lib/muchos/config.py
+++ b/lib/muchos/config.py
@@ -17,7 +17,7 @@ from sys import exit
 from util import get_ephemeral_devices, get_arch
 import os
 
-SERVICES = ['zookeeper', 'namenode', 'resourcemanager', 'accumulomaster', 'mesosmaster', 'worker', 'fluo', 'fluo_yarn', 'metrics', 'spark']
+SERVICES = ['zookeeper', 'namenode', 'resourcemanager', 'accumulomaster', 'mesosmaster', 'worker', 'fluo', 'fluo_yarn', 'metrics', 'spark', 'client']
 
 
 class DeployConfig(ConfigParser):
@@ -48,7 +48,7 @@ class DeployConfig(ConfigParser):
 
         if action in ['launch', 'setup']:
             for service in SERVICES:
-                if service not in ['fluo', 'fluo_yarn', 'metrics', 'mesosmaster', 'spark']:
+                if service not in ['fluo', 'fluo_yarn', 'metrics', 'mesosmaster', 'spark', 'client']:
                     if not self.has_service(service):
                         exit("ERROR - Missing '{0}' service from [nodes] section of muchos.props".format(service))