DolphinScheduler/ambari_plugin
rockxsj b6a0d55949
fix and update k8s deploy (#3215)
* 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>
2020-07-16 16:36:29 +08:00
..
common-services/DOLPHIN fix and update k8s deploy (#3215) 2020-07-16 16:36:29 +08:00
statcks/DOLPHIN update version 2.0.0 backup to 1.3.0 (#2531) 2020-04-26 18:50:38 +08:00
README.md [feature] readme.md adds instructions for changing environment variables (#3031) 2020-06-30 11:02:25 +08:00

Instructions for using the Dolphin Scheduler's Ambari plug-in

Note

  1. This document is intended for users with a basic understanding of Ambari
  2. This document is a description of adding the Dolphin Scheduler service to the installed Ambari service
  3. This document is based on version 2.5.2 of Ambari

Installation preparation

  1. 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 )
  2. Create an installation for DSwho have read and write access to the installation directory (/opt/soft)

  3. 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
  4. 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
  5. Initializes the database information

    -- Create the database for the Dolphin Schedulerdolphinscheduler
    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
  1. Install Dolphin Scheduler on ambari web interface

  2. Select the nodes for the Dolphin Scheduler's Master installation

  3. Configure the Dolphin Scheduler's nodes for Worker, Api, Logger, Alert installation

  4. Set the installation users of the Dolphin Scheduler service (created in step 1) and the user groups they belong to

  5. System Env Optimization will export some system environment config. Modify according to actual situation

  6. Configure the database information (same as in the initialization database in step 1)

  7. Configure additional information if needed

  8. Perform the next steps as normal

  9. 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)

  1. Locate the component node to add -- for example, node ark3

    DS2_AMBARI_011

  2. Add components -- the drop-down list is all addable

    DS2_AMBARI_012

  3. Confirm component addition

    DS2_AMBARI_013

  4. After adding DS Worker and DS Logger components

    DS2_AMBARI_015

  5. Start the component

    DS2_AMBARI_016

Remove the component from the node with Ambari

  1. Stop the component in the corresponding node

    DS2_AMBARI_018

  2. Remove components

    DS2_AMBARI_019