b6a0d55949
* Modify the AWS S3 request encryption method to V4. * * update Dockerfile to add mysql-client for mysql database service test * update wechat alert config replace placeholder from to {xx} because of the will be treat as env variable * fix unit test of EnterpriseWeChatUtilsTest * update values.yaml default config for helm deploy DS cluster * update values.yaml default config for custom install * update templates of helm for custom install * update some name of env varibale, for example change from POSTGRESQL_HOST to DATABASE_HOST * delele the redundancy requirements.yaml for heml * update README* in the docker dir and subdir * update startup scripts for support mysql as backend database * * fix the ENV name wrong in docker-compose.yml and docker-stack.yml * remove the didn't need port mapping in postgresql & zookeeper & dolphinscheduler-api * * keep expose the port of postgresql & zk & api because of unit test needed * * remove mysql-client package from dockerfile Co-authored-by: rockxsj <junjun@mgtv.com> |
||
---|---|---|
.. | ||
common-services/DOLPHIN | ||
statcks/DOLPHIN | ||
README.md |
Instructions for using the Dolphin Scheduler's Ambari plug-in
Note
- This document is intended for users with a basic understanding of Ambari
- This document is a description of adding the Dolphin Scheduler service to the installed Ambari service
- This document is based on version 2.5.2 of Ambari
Installation preparation
-
Prepare the RPM packages
- It is generated by executing the command
mvn -U clean install -Prpmbuild -Dmaven.test.skip=true -X
in the project root directory (In the directory: dolphinscheduler-dist/target/rpm/apache-dolphinscheduler-incubating/RPMS/noarch )
- It is generated by executing the command
-
Create an installation for DS,who have read and write access to the installation directory (/opt/soft)
-
Install with rpm package
-
Manual installation (recommended):
- Copy the prepared RPM packages to each node of the cluster.
- Execute with DS installation user:
rpm -ivh apache-dolphinscheduler-incubating-xxx.noarch.rpm
- Mysql-connector-java packaged using the default POM file will not be included.
- The RPM package was packaged in the project with the installation path of /opt/soft. If you use mysql as the database, you need add it manually.
-
Automatic installation with ambari
- Each node of the cluster needs to configure the local yum source
- Copy the prepared RPM packages to each node local yum source
-
-
Copy plug-in directory
- copy directory ambari_plugin/common-services/DOLPHIN to ambari-server/resources/common-services/
- copy directory ambari_plugin/statcks/DOLPHIN to ambari-server/resources/stacks/HDP/2.6/services/--stack version is selected based on the actual situation
-
Initializes the database information
-- Create the database for the Dolphin Scheduler:dolphinscheduler CREATE DATABASE dolphinscheduler DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci; -- Initialize the user and password for the dolphinscheduler database and assign permissions -- Replace the {user} in the SQL statement below with the user of the dolphinscheduler database GRANT ALL PRIVILEGES ON dolphinscheduler.* TO '{user}'@'%' IDENTIFIED BY '{password}'; GRANT ALL PRIVILEGES ON dolphinscheduler.* TO '{user}'@'localhost' IDENTIFIED BY '{password}'; flush privileges;
Ambari Install Dolphin Scheduler
- NOTE: You have to install zookeeper first
-
Install Dolphin Scheduler on ambari web interface
-
Select the nodes for the Dolphin Scheduler's Master installation
-
Configure the Dolphin Scheduler's nodes for Worker, Api, Logger, Alert installation
-
Set the installation users of the Dolphin Scheduler service (created in step 1) and the user groups they belong to
-
System Env Optimization will export some system environment config. Modify according to actual situation
-
Configure the database information (same as in the initialization database in step 1)
-
Configure additional information if needed
-
Perform the next steps as normal
-
The interface after successful installation
Add components to the node through Ambari -- for example, add a DS Worker
NOTE: DS Logger is the installation dependent component of DS Worker in Dolphin's Ambari installation (need to add installation first; Prevent the Job log on the corresponding Worker from being checked)
-
Locate the component node to add -- for example, node ark3
-
Add components -- the drop-down list is all addable
-
Confirm component addition
-
After adding DS Worker and DS Logger components
-
Start the component