In this tutorial we will going to setup Odysseus Studio with OdysseusNet capabilities and start it as a master node. Then worker nodes are started with docker-compose and will be dynamically added to the master node with OdysseusNet in Odysseus Studio. At next queries will be remotely executed on the worker nodes from the master node.
Setup Odysseus with Development with Odysseus, but change the following
Now you have installed the target platform, before you launch the product, we are going to add the OdysseusNet monolithic target to the normal monolithic target (see for a general tutorial Adding features to products) :
The OdysseusNet monolithic target also includes the OdysseusNet server target.
If successfully started you can close Odysseus Studio for now for changing OdysseusNet config under ODYSSEUS_HOME (OdysseusNet Configuration)
With Linux the ODYSSEUS_HOME is ~/.odysseus, there you can change the odysseusNet.config to
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> <properties> <comment>OdysseusNet Property File edit only if you know what you are doing</comment> <entry key="net.networkoperatorgenerator">websocket</entry> <entry key="net.node.default.username">System</entry> <entry key="net.dd.local">true</entry> <entry key="net.node.name">OdysseusNode_1554</entry> <entry key="net.discoverer.name">BroadcastOdysseusNodeDiscoverer,IPListOdysseusNodeDiscoverer</entry> <entry key="net.querydistribute.allocation">querycount</entry> <entry key="net.source.lifetime">3600000</entry> <entry key="net.connect.selector.name">GroupSelectorComponent</entry> <entry key="net.nodemanager.storetype">filestore</entry> <entry key="net.nodemanager.filename">/home/$USER/.odysseus/store/nodes.store</entry> <entry key="net.dd.checkinterval">30000</entry> <entry key="net.remoteUpdate">false</entry> <entry key="net.node.communicator">rest</entry> <entry key="net.node.preserveid">false</entry> <entry key="net.querydistribute.minport">10000</entry> <entry key="net.autostart">true</entry> <entry key="net.querydistribute.partition">querycloud</entry> <entry key="net.querydistribute.randomport">false</entry> <entry key="net.discoverer.interval">5000</entry> <entry key="net.node.default.password">manager</entry> <entry key="net.node.group">OdysseusGroup</entry> <entry key="net.querydistribute.maxport">20000</entry> <entry key="net.logging.receive">false</entry> </properties> |
Replace $USER with your local user
Now we start Nexmark (a data stream simulation tool, see Getting Started with Nexmark) and Odysseus worker nodes with docker-compose, therefore create a docker-compose.yml in a directory (it will be named $CURRENT_DIRECTORY here for reference, in practice it could be e. g. the odysseusnet-repo) and with the following content (adopted from OdysseusNet Docker Compose Example):
version: '3.3' services: nexmark: image: odysseusol/nexmark ports: - 65440-65443:65440-65443 worker01: image: odysseusol/odysseusnet stdin_open: true ports: - 18881:8888 volumes: - ./worker01:/var/lib/odysseus worker02: image: odysseusol/odysseusnet stdin_open: true ports: - 18882:8888 volumes: - ./worker02:/var/lib/odysseus worker03: image: odysseusol/odysseusnet stdin_open: true ports: - 18883:8888 volumes: - ./worker03:/var/lib/odysseus |
As a workaround make sure the worker01-03 directories have the 777-permissions with:
sudo chmod 777 -R worker0* |
Otherwise the internal Odysseus worker node user cannot access the volume properly and fails.
All configuration files will be placed under the $CURRENT_DIRECTORY, e. g. there are the following files: logs odysseus.conf odysseusNet.conf reloadlog.store scheduling.conf store |