分布式调度框架。
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Wenjun Ruan 9448806af0
[DSIP-61][Master] Refactor thread pool and state event orchestration in master (#16327)
3 months ago
..
src [DSIP-61][Master] Refactor thread pool and state event orchestration in master (#16327) 3 months ago
README.md [DSIP-56] Refactor JDBC registry support session timeout and data change event (#16287) 5 months ago
pom.xml Add IntegretionTest for registry module (#15981) 7 months ago

README.md

Introduction

This module is the jdbc registry plugin module, this plugin will use jdbc as the registry center. Will use the database configuration same as DolphinScheduler in api'yaml default.

How to use

  1. Initialize the database table
  • If you use Mysql you can directly execute the sql script src/main/resources/mysql_registry_init.sql.

  • If you use Postgresql you can directly execute the sql script src/main/resources/postgresql_registry_init.sql.

  1. Change the config

You need to set the registry properties in master/worker/api's application.yml

registry:
  type: jdbc

After do this two steps, you can start your DolphinScheduler cluster, your cluster will use mysql as registry center to store server metadata.

NOTE: You need to add mysql-connector-java.jar into DS classpath if you use mysql database, since this plugin will not bundle this driver in distribution. You can get the detail about Initialize the Database.

Optional configuration

registry:
  type: jdbc
  # Used to schedule refresh the heartbeat.
  heartbeat-refresh-interval: 3s
  # Once the client's heartbeat is not refresh in this time, the server will consider the client is offline.
  session-timeout: 60s
  # The hikari configuration, default will use the same datasource pool as DolphinScheduler.
  hikari-config:
    jdbc-url: jdbc:mysql://127.0.0.1:3306/dolphinscheduler
    username: root
    password: root
    maximum-pool-size: 5
    connection-timeout: 9000
    idle-timeout: 600000

Use different database configuration for jdbc registry center

You need to set the registry properties in master/worker/api's application.yml

Use Mysql as registry center

registry:
  type: jdbc
  heartbeat-refresh-interval: 3s
  session-timeout: 60s
  hikari-config:
    jdbc-url: jdbc:mysql://127.0.0.1:3306/dolphinscheduler
    username: root
    password: root
    maximum-pool-size: 5
    connection-timeout: 9000
    idle-timeout: 600000

Use Postgresql as registry center

registry:
  type: jdbc
  heartbeat-refresh-interval: 3s
  session-timeout: 60s
  hikari-config:
    jdbc-url: jdbc:postgresql://localhost:5432/dolphinscheduler
    username: root
    password: root
    maximum-pool-size: 5
    connection-timeout: 9000
    idle-timeout: 600000