lgcareer
5 years ago
64 changed files with 212 additions and 1084 deletions
@ -1,145 +0,0 @@
|
||||
FROM ubuntu:18.04 |
||||
|
||||
MAINTAINER journey "825193156@qq.com" |
||||
|
||||
ENV LANG=C.UTF-8 |
||||
|
||||
ARG version |
||||
|
||||
#1,安装jdk |
||||
|
||||
RUN apt-get update \ |
||||
&& apt-get -y install openjdk-8-jdk \ |
||||
&& rm -rf /var/lib/apt/lists/* |
||||
|
||||
ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64 |
||||
ENV PATH $JAVA_HOME/bin:$PATH |
||||
|
||||
|
||||
#安装wget |
||||
RUN apt-get update && \ |
||||
apt-get -y install wget |
||||
#2,安装ZK |
||||
#RUN cd /opt && \ |
||||
# wget https://archive.apache.org/dist/zookeeper/zookeeper-3.4.6/zookeeper-3.4.6.tar.gz && \ |
||||
# tar -zxvf zookeeper-3.4.6.tar.gz && \ |
||||
# mv zookeeper-3.4.6 zookeeper && \ |
||||
# rm -rf ./zookeeper-*tar.gz && \ |
||||
# mkdir -p /tmp/zookeeper && \ |
||||
# rm -rf /opt/zookeeper/conf/zoo_sample.cfg |
||||
|
||||
RUN cd /opt && \ |
||||
wget https://www-us.apache.org/dist/zookeeper/zookeeper-3.4.14/zookeeper-3.4.14.tar.gz && \ |
||||
tar -zxvf zookeeper-3.4.14.tar.gz && \ |
||||
mv zookeeper-3.4.14 zookeeper && \ |
||||
rm -rf ./zookeeper-*tar.gz && \ |
||||
mkdir -p /tmp/zookeeper && \ |
||||
rm -rf /opt/zookeeper/conf/zoo_sample.cfg |
||||
|
||||
ADD ./conf/zookeeper/zoo.cfg /opt/zookeeper/conf |
||||
ENV ZK_HOME=/opt/zookeeper |
||||
ENV PATH $PATH:$ZK_HOME/bin |
||||
|
||||
#3,安装maven |
||||
RUN cd /opt && \ |
||||
wget http://apache-mirror.rbc.ru/pub/apache/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz && \ |
||||
tar -zxvf apache-maven-3.3.9-bin.tar.gz && \ |
||||
mv apache-maven-3.3.9 maven && \ |
||||
rm -rf ./apache-maven-*tar.gz && \ |
||||
rm -rf /opt/maven/conf/settings.xml |
||||
ADD ./conf/maven/settings.xml /opt/maven/conf |
||||
ENV MAVEN_HOME=/opt/maven |
||||
ENV PATH $PATH:$MAVEN_HOME/bin |
||||
|
||||
#4,安装node |
||||
RUN cd /opt && \ |
||||
wget https://nodejs.org/download/release/v8.9.4/node-v8.9.4-linux-x64.tar.gz && \ |
||||
tar -zxvf node-v8.9.4-linux-x64.tar.gz && \ |
||||
mv node-v8.9.4-linux-x64 node && \ |
||||
rm -rf ./node-v8.9.4-*tar.gz |
||||
ENV NODE_HOME=/opt/node |
||||
ENV PATH $PATH:$NODE_HOME/bin |
||||
|
||||
#5,下载escheduler |
||||
RUN cd /opt && \ |
||||
wget https://github.com/analysys/EasyScheduler/archive/${version}.tar.gz && \ |
||||
tar -zxvf ${version}.tar.gz && \ |
||||
mv EasyScheduler-${version} easyscheduler_source && \ |
||||
rm -rf ./${version}.tar.gz |
||||
|
||||
#6,后端编译 |
||||
RUN cd /opt/easyscheduler_source && \ |
||||
mvn -U clean package assembly:assembly -Dmaven.test.skip=true |
||||
|
||||
#7,前端编译 |
||||
RUN chmod -R 777 /opt/easyscheduler_source/escheduler-ui && \ |
||||
cd /opt/easyscheduler_source/escheduler-ui && \ |
||||
rm -rf /opt/easyscheduler_source/escheduler-ui/node_modules && \ |
||||
npm install node-sass --unsafe-perm && \ |
||||
npm install && \ |
||||
npm run build |
||||
#8,安装mysql |
||||
RUN echo "deb http://cn.archive.ubuntu.com/ubuntu/ xenial main restricted universe multiverse" >> /etc/apt/sources.list |
||||
|
||||
RUN echo "mysql-server mysql-server/root_password password root" | debconf-set-selections |
||||
RUN echo "mysql-server mysql-server/root_password_again password root" | debconf-set-selections |
||||
|
||||
RUN apt-get update && \ |
||||
apt-get -y install mysql-server-5.7 && \ |
||||
mkdir -p /var/lib/mysql && \ |
||||
mkdir -p /var/run/mysqld && \ |
||||
mkdir -p /var/log/mysql && \ |
||||
chown -R mysql:mysql /var/lib/mysql && \ |
||||
chown -R mysql:mysql /var/run/mysqld && \ |
||||
chown -R mysql:mysql /var/log/mysql |
||||
|
||||
|
||||
# UTF-8 and bind-address |
||||
RUN sed -i -e "$ a [client]\n\n[mysql]\n\n[mysqld]" /etc/mysql/my.cnf && \ |
||||
sed -i -e "s/\(\[client\]\)/\1\ndefault-character-set = utf8/g" /etc/mysql/my.cnf && \ |
||||
sed -i -e "s/\(\[mysql\]\)/\1\ndefault-character-set = utf8/g" /etc/mysql/my.cnf && \ |
||||
sed -i -e "s/\(\[mysqld\]\)/\1\ninit_connect='SET NAMES utf8'\ncharacter-set-server = utf8\ncollation-server=utf8_general_ci\nbind-address = 0.0.0.0/g" /etc/mysql/my.cnf |
||||
|
||||
|
||||
#9,安装nginx |
||||
RUN apt-get update && \ |
||||
apt-get install -y nginx && \ |
||||
rm -rf /var/lib/apt/lists/* && \ |
||||
echo "\ndaemon off;" >> /etc/nginx/nginx.conf && \ |
||||
chown -R www-data:www-data /var/lib/nginx |
||||
|
||||
#10,修改escheduler配置文件 |
||||
#后端配置 |
||||
RUN mkdir -p /opt/escheduler && \ |
||||
tar -zxvf /opt/easyscheduler_source/target/escheduler-${version}.tar.gz -C /opt/escheduler && \ |
||||
rm -rf /opt/escheduler/conf |
||||
ADD ./conf/escheduler/conf /opt/escheduler/conf |
||||
#前端nginx配置 |
||||
ADD ./conf/nginx/default.conf /etc/nginx/conf.d |
||||
|
||||
#11,开放端口 |
||||
EXPOSE 2181 2888 3888 3306 80 12345 8888 |
||||
|
||||
#12,安装sudo,python,vim,ping和ssh |
||||
RUN apt-get update && \ |
||||
apt-get -y install sudo && \ |
||||
apt-get -y install python && \ |
||||
apt-get -y install vim && \ |
||||
apt-get -y install iputils-ping && \ |
||||
apt-get -y install net-tools && \ |
||||
apt-get -y install openssh-server && \ |
||||
apt-get -y install python-pip && \ |
||||
pip install kazoo |
||||
|
||||
COPY ./startup.sh /root/startup.sh |
||||
#13,修改权限和设置软连 |
||||
RUN chmod +x /root/startup.sh && \ |
||||
chmod +x /opt/escheduler/script/create_escheduler.sh && \ |
||||
chmod +x /opt/zookeeper/bin/zkServer.sh && \ |
||||
chmod +x /opt/escheduler/bin/escheduler-daemon.sh && \ |
||||
rm -rf /bin/sh && \ |
||||
ln -s /bin/bash /bin/sh && \ |
||||
mkdir -p /tmp/xls |
||||
|
||||
|
||||
ENTRYPOINT ["/root/startup.sh"] |
||||
@ -1,21 +0,0 @@
|
||||
#alert type is EMAIL/SMS |
||||
alert.type=EMAIL |
||||
|
||||
# mail server configuration |
||||
mail.protocol=SMTP |
||||
mail.server.host=smtp.office365.com |
||||
mail.server.port=587 |
||||
mail.sender=qiaozhanwei@outlook.com |
||||
mail.passwd=eschedulerBJEG |
||||
|
||||
# TLS |
||||
mail.smtp.starttls.enable=true |
||||
# SSL |
||||
mail.smtp.ssl.enable=false |
||||
|
||||
#xls file path,need create if not exist |
||||
xls.file.path=/tmp/xls |
||||
|
||||
|
||||
|
||||
|
||||
@ -1,16 +0,0 @@
|
||||
# server port |
||||
server.port=12345 |
||||
|
||||
# session config |
||||
server.session.timeout=7200 |
||||
|
||||
|
||||
server.context-path=/escheduler/ |
||||
|
||||
# file size limit for upload |
||||
spring.http.multipart.max-file-size=1024MB |
||||
spring.http.multipart.max-request-size=1024MB |
||||
|
||||
#post content |
||||
server.max-http-post-size=5000000 |
||||
|
||||
@ -1,27 +0,0 @@
|
||||
#task queue implementation, default "zookeeper" |
||||
escheduler.queue.impl=zookeeper |
||||
|
||||
# user data directory path, self configuration, please make sure the directory exists and have read write permissions |
||||
data.basedir.path=/tmp/escheduler |
||||
|
||||
# directory path for user data download. self configuration, please make sure the directory exists and have read write permissions |
||||
data.download.basedir.path=/tmp/escheduler/download |
||||
|
||||
# process execute directory. self configuration, please make sure the directory exists and have read write permissions |
||||
process.exec.basepath=/tmp/escheduler/exec |
||||
|
||||
# data base dir, resource file will store to this hadoop hdfs path, self configuration, please make sure the directory exists on hdfs and have read write permissions。"/escheduler" is recommended |
||||
data.store2hdfs.basepath=/escheduler |
||||
|
||||
# whether hdfs starts |
||||
hdfs.startup.state=false |
||||
|
||||
# system env path. self configuration, please make sure the directory and file exists and have read write execute permissions |
||||
escheduler.env.path=/opt/escheduler/conf/env/.escheduler_env.sh |
||||
|
||||
#resource.view.suffixs |
||||
resource.view.suffixs=txt,log,sh,conf,cfg,py,java,sql,hql,xml |
||||
|
||||
# is development state? default "false" |
||||
development.state=false |
||||
|
||||
@ -1,8 +0,0 @@
|
||||
# ha or single namenode,If namenode ha needs to copy core-site.xml and hdfs-site.xml to the conf directory |
||||
fs.defaultFS=hdfs://mycluster:8020 |
||||
|
||||
#resourcemanager ha note this need ips , this empty if single |
||||
yarn.resourcemanager.ha.rm.ids=192.168.xx.xx,192.168.xx.xx |
||||
|
||||
# If it is a single resourcemanager, you only need to configure one host name. If it is resourcemanager HA, the default configuration is fine |
||||
yarn.application.status.address=http://ark1:8088/ws/v1/cluster/apps/%s |
||||
@ -1,4 +0,0 @@
|
||||
export PYTHON_HOME=/usr/bin/python |
||||
export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 |
||||
|
||||
export PATH=$PYTHON_HOME:$JAVA_HOME/bin:$PATH |
||||
@ -1,39 +0,0 @@
|
||||
#============================================================================ |
||||
# Configure Main Scheduler Properties |
||||
#============================================================================ |
||||
org.quartz.scheduler.instanceName = EasyScheduler |
||||
org.quartz.scheduler.instanceId = AUTO |
||||
org.quartz.scheduler.makeSchedulerThreadDaemon = true |
||||
org.quartz.jobStore.useProperties = false |
||||
|
||||
#============================================================================ |
||||
# Configure ThreadPool |
||||
#============================================================================ |
||||
|
||||
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool |
||||
org.quartz.threadPool.makeThreadsDaemons = true |
||||
org.quartz.threadPool.threadCount = 25 |
||||
org.quartz.threadPool.threadPriority = 5 |
||||
|
||||
#============================================================================ |
||||
# Configure JobStore |
||||
#============================================================================ |
||||
|
||||
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX |
||||
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate |
||||
org.quartz.jobStore.tablePrefix = QRTZ_ |
||||
org.quartz.jobStore.isClustered = true |
||||
org.quartz.jobStore.misfireThreshold = 60000 |
||||
org.quartz.jobStore.clusterCheckinInterval = 5000 |
||||
org.quartz.jobStore.dataSource = myDs |
||||
|
||||
#============================================================================ |
||||
# Configure Datasources |
||||
#============================================================================ |
||||
|
||||
org.quartz.dataSource.myDs.driver = com.mysql.jdbc.Driver |
||||
org.quartz.dataSource.myDs.URL = jdbc:mysql://127.0.0.1:3306/escheduler?characterEncoding=utf8 |
||||
org.quartz.dataSource.myDs.user = root |
||||
org.quartz.dataSource.myDs.password = root@123 |
||||
org.quartz.dataSource.myDs.maxConnections = 10 |
||||
org.quartz.dataSource.myDs.validationQuery = select 1 |
||||
@ -1,25 +0,0 @@
|
||||
#zookeeper cluster |
||||
zookeeper.quorum=127.0.0.1:2181 |
||||
|
||||
#escheduler root directory |
||||
zookeeper.escheduler.root=/escheduler |
||||
|
||||
#zookeeper server dirctory |
||||
zookeeper.escheduler.dead.servers=/escheduler/dead-servers |
||||
zookeeper.escheduler.masters=/escheduler/masters |
||||
zookeeper.escheduler.workers=/escheduler/workers |
||||
|
||||
#zookeeper lock dirctory |
||||
zookeeper.escheduler.lock.masters=/escheduler/lock/masters |
||||
zookeeper.escheduler.lock.workers=/escheduler/lock/workers |
||||
|
||||
#escheduler failover directory |
||||
zookeeper.escheduler.lock.failover.masters=/escheduler/lock/failover/masters |
||||
zookeeper.escheduler.lock.failover.workers=/escheduler/lock/failover/workers |
||||
zookeeper.escheduler.lock.failover.startup.masters=/escheduler/lock/failover/startup-masters |
||||
|
||||
#escheduler failover directory |
||||
zookeeper.session.timeout=300 |
||||
zookeeper.connection.timeout=300 |
||||
zookeeper.retry.sleep=1000 |
||||
zookeeper.retry.maxtime=5 |
||||
@ -1,8 +0,0 @@
|
||||
#!/bin/bash |
||||
|
||||
echo "------ escheduler start - build -------" |
||||
printenv |
||||
|
||||
docker build --build-arg version=$version -t $DOCKER_REPO:$version . |
||||
|
||||
echo "------ escheduler end - build -------" |
||||
@ -1,79 +0,0 @@
|
||||
#! /bin/bash |
||||
|
||||
set -e |
||||
if [ `netstat -anop|grep mysql|wc -l` -gt 0 ];then |
||||
echo "MySQL is Running." |
||||
else |
||||
MYSQL_ROOT_PWD="root@123" |
||||
ESZ_DB="escheduler" |
||||
echo "启动mysql服务" |
||||
chown -R mysql:mysql /var/lib/mysql /var/run/mysqld |
||||
find /var/lib/mysql -type f -exec touch {} \; && service mysql restart $ sleep 10 |
||||
if [ ! -f /nohup.out ];then |
||||
echo "设置mysql密码" |
||||
mysql --user=root --password=root -e "UPDATE mysql.user set authentication_string=password('$MYSQL_ROOT_PWD') where user='root'; FLUSH PRIVILEGES;" |
||||
|
||||
echo "设置mysql权限" |
||||
mysql --user=root --password=$MYSQL_ROOT_PWD -e "GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY '$MYSQL_ROOT_PWD' WITH GRANT OPTION; FLUSH PRIVILEGES;" |
||||
echo "创建escheduler数据库" |
||||
mysql --user=root --password=$MYSQL_ROOT_PWD -e "CREATE DATABASE IF NOT EXISTS \`$ESZ_DB\` CHARACTER SET utf8 COLLATE utf8_general_ci; FLUSH PRIVILEGES;" |
||||
echo "导入mysql数据" |
||||
nohup /opt/escheduler/script/create_escheduler.sh & |
||||
fi |
||||
|
||||
if [ `mysql --user=root --password=$MYSQL_ROOT_PWD -s -r -e "SELECT count(TABLE_NAME) FROM information_schema.TABLES WHERE TABLE_SCHEMA='escheduler';" | grep -v count` -eq 38 ];then |
||||
echo "\`$ESZ_DB\` 表个数正确" |
||||
else |
||||
echo "\`$ESZ_DB\` 表个数不正确" |
||||
mysql --user=root --password=$MYSQL_ROOT_PWD -e "DROP DATABASE \`$ESZ_DB\`;" |
||||
echo "创建escheduler数据库" |
||||
mysql --user=root --password=$MYSQL_ROOT_PWD -e "CREATE DATABASE IF NOT EXISTS \`$ESZ_DB\` CHARACTER SET utf8 COLLATE utf8_general_ci; FLUSH PRIVILEGES;" |
||||
echo "导入mysql数据" |
||||
nohup /opt/escheduler/script/create_escheduler.sh & |
||||
fi |
||||
fi |
||||
|
||||
/opt/zookeeper/bin/zkServer.sh restart |
||||
|
||||
sleep 10 |
||||
|
||||
echo "启动api-server" |
||||
/opt/escheduler/bin/escheduler-daemon.sh stop api-server |
||||
/opt/escheduler/bin/escheduler-daemon.sh start api-server |
||||
|
||||
|
||||
|
||||
echo "启动master-server" |
||||
/opt/escheduler/bin/escheduler-daemon.sh stop master-server |
||||
python /opt/escheduler/script/del_zk_node.py 127.0.0.1 /escheduler/masters |
||||
/opt/escheduler/bin/escheduler-daemon.sh start master-server |
||||
|
||||
echo "启动worker-server" |
||||
/opt/escheduler/bin/escheduler-daemon.sh stop worker-server |
||||
python /opt/escheduler/script/del_zk_node.py 127.0.0.1 /escheduler/workers |
||||
/opt/escheduler/bin/escheduler-daemon.sh start worker-server |
||||
|
||||
|
||||
echo "启动logger-server" |
||||
/opt/escheduler/bin/escheduler-daemon.sh stop logger-server |
||||
/opt/escheduler/bin/escheduler-daemon.sh start logger-server |
||||
|
||||
|
||||
echo "启动alert-server" |
||||
/opt/escheduler/bin/escheduler-daemon.sh stop alert-server |
||||
/opt/escheduler/bin/escheduler-daemon.sh start alert-server |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
echo "启动nginx" |
||||
/etc/init.d/nginx stop |
||||
nginx & |
||||
|
||||
|
||||
while true |
||||
do |
||||
sleep 101 |
||||
done |
||||
exec "$@" |
||||
@ -1,31 +0,0 @@
|
||||
<!-- Logback configuration. See http://logback.qos.ch/manual/index.html --> |
||||
<configuration scan="true" scanPeriod="120 seconds"> <!--debug="true" --> |
||||
<property name="log.base" value="logs" /> |
||||
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> |
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
</appender> |
||||
|
||||
<appender name="ALERTLOGFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> |
||||
<file>${log.base}/escheduler-alert.log</file> |
||||
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> |
||||
<fileNamePattern>${log.base}/escheduler-alert.%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern> |
||||
<maxHistory>20</maxHistory> |
||||
<maxFileSize>64MB</maxFileSize> |
||||
</rollingPolicy> |
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
</appender> |
||||
|
||||
<root level="INFO"> |
||||
<appender-ref ref="ALERTLOGFILE"/> |
||||
</root> |
||||
</configuration> |
||||
@ -1,42 +0,0 @@
|
||||
<!-- Logback configuration. See http://logback.qos.ch/manual/index.html --> |
||||
<configuration scan="true" scanPeriod="120 seconds"> |
||||
<logger name="org.apache.zookeeper" level="WARN"/> |
||||
<logger name="org.apache.hbase" level="WARN"/> |
||||
<logger name="org.apache.hadoop" level="WARN"/> |
||||
|
||||
<property name="log.base" value="logs" /> |
||||
|
||||
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> |
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
</appender> |
||||
|
||||
<appender name="APISERVERLOGFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> |
||||
<!-- Log level filter --> |
||||
<filter class="ch.qos.logback.classic.filter.ThresholdFilter"> |
||||
<level>INFO</level> |
||||
</filter> |
||||
<file>${log.base}/escheduler-api-server.log</file> |
||||
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> |
||||
<fileNamePattern>${log.base}/escheduler-api-server.%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern> |
||||
<maxHistory>168</maxHistory> |
||||
<maxFileSize>64MB</maxFileSize> |
||||
</rollingPolicy> |
||||
|
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
|
||||
</appender> |
||||
|
||||
<root level="INFO"> |
||||
<appender-ref ref="APISERVERLOGFILE" /> |
||||
</root> |
||||
</configuration> |
||||
@ -1 +0,0 @@
|
||||
logging.config=classpath:master_logback.xml |
||||
@ -1,3 +0,0 @@
|
||||
installPath=/data1_1T/escheduler |
||||
deployUser=escheduler |
||||
ips=ark0,ark1,ark2,ark3,ark4 |
||||
@ -1,4 +0,0 @@
|
||||
masters=ark0,ark1 |
||||
workers=ark2,ark3,ark4 |
||||
alertServer=ark3 |
||||
apiServers=ark1 |
||||
@ -1,53 +0,0 @@
|
||||
# base spring data source configuration |
||||
spring.datasource.type=com.alibaba.druid.pool.DruidDataSource |
||||
spring.datasource.driver-class-name=com.mysql.jdbc.Driver |
||||
spring.datasource.url=jdbc:mysql://127.0.0.1:3306/escheduler?characterEncoding=UTF-8 |
||||
spring.datasource.username=root |
||||
spring.datasource.password=root@123 |
||||
|
||||
# connection configuration |
||||
spring.datasource.initialSize=5 |
||||
# min connection number |
||||
spring.datasource.minIdle=5 |
||||
# max connection number |
||||
spring.datasource.maxActive=50 |
||||
|
||||
# max wait time for get a connection in milliseconds. if configuring maxWait, fair locks are enabled by default and concurrency efficiency decreases. |
||||
# If necessary, unfair locks can be used by configuring the useUnfairLock attribute to true. |
||||
spring.datasource.maxWait=60000 |
||||
|
||||
# milliseconds for check to close free connections |
||||
spring.datasource.timeBetweenEvictionRunsMillis=60000 |
||||
|
||||
# the Destroy thread detects the connection interval and closes the physical connection in milliseconds if the connection idle time is greater than or equal to minEvictableIdleTimeMillis. |
||||
spring.datasource.timeBetweenConnectErrorMillis=60000 |
||||
|
||||
# the longest time a connection remains idle without being evicted, in milliseconds |
||||
spring.datasource.minEvictableIdleTimeMillis=300000 |
||||
|
||||
#the SQL used to check whether the connection is valid requires a query statement. If validation Query is null, testOnBorrow, testOnReturn, and testWhileIdle will not work. |
||||
spring.datasource.validationQuery=SELECT 1 |
||||
#check whether the connection is valid for timeout, in seconds |
||||
spring.datasource.validationQueryTimeout=3 |
||||
|
||||
# when applying for a connection, if it is detected that the connection is idle longer than time Between Eviction Runs Millis, |
||||
# validation Query is performed to check whether the connection is valid |
||||
spring.datasource.testWhileIdle=true |
||||
|
||||
#execute validation to check if the connection is valid when applying for a connection |
||||
spring.datasource.testOnBorrow=true |
||||
#execute validation to check if the connection is valid when the connection is returned |
||||
spring.datasource.testOnReturn=false |
||||
spring.datasource.defaultAutoCommit=true |
||||
spring.datasource.keepAlive=true |
||||
|
||||
# open PSCache, specify count PSCache for every connection |
||||
spring.datasource.poolPreparedStatements=true |
||||
spring.datasource.maxPoolPreparedStatementPerConnectionSize=20 |
||||
|
||||
# data quality analysis is not currently in use. please ignore the following configuration |
||||
# task record flag |
||||
task.record.flag=false |
||||
task.record.datasource.url=jdbc:mysql://192.168.xx.xx:3306/etl?characterEncoding=UTF-8 |
||||
task.record.datasource.username=xx |
||||
task.record.datasource.password=xx |
||||
@ -1 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'><html><head><title> easyscheduler</title><meta name='Keywords' content=''><meta name='Description' content=''><style type="text/css">table { margin-top:0px; padding-top:0px; border:1px solid; font-size: 14px; color: #333333; border-width: 1px; border-color: #666666; border-collapse: collapse; } table th { border-width: 1px; padding: 8px; border-style: solid; border-color: #666666; background-color: #dedede; } table td { border-width: 1px; padding: 8px; border-style: solid; border-color: #666666; background-color: #ffffff; }</style></head><body style="margin:0;padding:0"><table border="1px" cellpadding="5px" cellspacing="-10px"><thead><#if title??> ${title}</#if></thead><#if content??> ${content}</#if></table></body></html> |
||||
@ -1,21 +0,0 @@
|
||||
# master execute thread num |
||||
master.exec.threads=100 |
||||
|
||||
# master execute task number in parallel |
||||
master.exec.task.number=20 |
||||
|
||||
# master heartbeat interval |
||||
master.heartbeat.interval=10 |
||||
|
||||
# master commit task retry times |
||||
master.task.commit.retryTimes=5 |
||||
|
||||
# master commit task interval |
||||
master.task.commit.interval=100 |
||||
|
||||
|
||||
# only less than cpu avg load, master server can work. default value : the number of cpu cores * 2 |
||||
master.max.cpuload.avg=10 |
||||
|
||||
# only larger than reserved memory, master server can work. default value : physical memory * 1/10, unit is G. |
||||
master.reserved.memory=1 |
||||
@ -1,34 +0,0 @@
|
||||
<!-- Logback configuration. See http://logback.qos.ch/manual/index.html --> |
||||
<configuration scan="true" scanPeriod="120 seconds"> <!--debug="true" --> |
||||
<property name="log.base" value="logs" /> |
||||
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> |
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
</appender> |
||||
|
||||
<appender name="MASTERLOGFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> |
||||
<file>${log.base}/escheduler-master.log</file> |
||||
<filter class="cn.escheduler.server.master.log.MasterLogFilter"> |
||||
<level>INFO</level> |
||||
</filter> |
||||
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> |
||||
<fileNamePattern>${log.base}/escheduler-master.%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern> |
||||
<maxHistory>168</maxHistory> |
||||
<maxFileSize>200MB</maxFileSize> |
||||
</rollingPolicy> |
||||
<encoder> |
||||
<pattern> |
||||
[%level] %date{yyyy-MM-dd HH:mm:ss.SSS} %logger{96}:[%line] - %msg%n |
||||
</pattern> |
||||
<charset>UTF-8</charset> |
||||
</encoder> |
||||
</appender> |
||||
|
||||
<root level="INFO"> |
||||
<appender-ref ref="MASTERLOGFILE"/> |
||||
</root> |
||||
</configuration> |
||||
@ -1,15 +0,0 @@
|
||||
# worker execute thread num |
||||
worker.exec.threads=100 |
||||
|
||||
# worker heartbeat interval |
||||
worker.heartbeat.interval=10 |
||||
|
||||
# submit the number of tasks at a time |
||||
worker.fetch.task.num = 3 |
||||
|
||||
|
||||
# only less than cpu avg load, worker server can work. default value : the number of cpu cores * 2 |
||||
#worker.max.cpuload.avg=10 |
||||
|
||||
# only larger than reserved memory, worker server can work. default value : physical memory * 1/6, unit is G. |
||||
worker.reserved.memory=1 |
||||
@ -1,263 +0,0 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
|
||||
<!-- |
||||
Licensed to the Apache Software Foundation (ASF) under one |
||||
or more contributor license agreements. See the NOTICE file |
||||
distributed with this work for additional information |
||||
regarding copyright ownership. The ASF licenses this file |
||||
to you under the Apache License, Version 2.0 (the |
||||
"License"); you may not use this file except in compliance |
||||
with the License. You may obtain a copy of the License at |
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0 |
||||
|
||||
Unless required by applicable law or agreed to in writing, |
||||
software distributed under the License is distributed on an |
||||
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
||||
KIND, either express or implied. See the License for the |
||||
specific language governing permissions and limitations |
||||
under the License. |
||||
--> |
||||
|
||||
<!-- |
||||
| This is the configuration file for Maven. It can be specified at two levels: |
||||
| |
||||
| 1. User Level. This settings.xml file provides configuration for a single user, |
||||
| and is normally provided in ${user.home}/.m2/settings.xml. |
||||
| |
||||
| NOTE: This location can be overridden with the CLI option: |
||||
| |
||||
| -s /path/to/user/settings.xml |
||||
| |
||||
| 2. Global Level. This settings.xml file provides configuration for all Maven |
||||
| users on a machine (assuming they're all using the same Maven |
||||
| installation). It's normally provided in |
||||
| ${maven.home}/conf/settings.xml. |
||||
| |
||||
| NOTE: This location can be overridden with the CLI option: |
||||
| |
||||
| -gs /path/to/global/settings.xml |
||||
| |
||||
| The sections in this sample file are intended to give you a running start at |
||||
| getting the most out of your Maven installation. Where appropriate, the default |
||||
| values (values used when the setting is not specified) are provided. |
||||
| |
||||
|--> |
||||
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" |
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
||||
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> |
||||
<!-- localRepository |
||||
| The path to the local repository maven will use to store artifacts. |
||||
| |
||||
| Default: ${user.home}/.m2/repository |
||||
<localRepository>/path/to/local/repo</localRepository> |
||||
--> |
||||
|
||||
<!-- interactiveMode |
||||
| This will determine whether maven prompts you when it needs input. If set to false, |
||||
| maven will use a sensible default value, perhaps based on some other setting, for |
||||
| the parameter in question. |
||||
| |
||||
| Default: true |
||||
<interactiveMode>true</interactiveMode> |
||||
--> |
||||
|
||||
<!-- offline |
||||
| Determines whether maven should attempt to connect to the network when executing a build. |
||||
| This will have an effect on artifact downloads, artifact deployment, and others. |
||||
| |
||||
| Default: false |
||||
<offline>false</offline> |
||||
--> |
||||
|
||||
<!-- pluginGroups |
||||
| This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e. |
||||
| when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers |
||||
| "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list. |
||||
|--> |
||||
<pluginGroups> |
||||
<!-- pluginGroup |
||||
| Specifies a further group identifier to use for plugin lookup. |
||||
<pluginGroup>com.your.plugins</pluginGroup> |
||||
--> |
||||
</pluginGroups> |
||||
|
||||
<!-- proxies |
||||
| This is a list of proxies which can be used on this machine to connect to the network. |
||||
| Unless otherwise specified (by system property or command-line switch), the first proxy |
||||
| specification in this list marked as active will be used. |
||||
|--> |
||||
<proxies> |
||||
<!-- proxy |
||||
| Specification for one proxy, to be used in connecting to the network. |
||||
| |
||||
<proxy> |
||||
<id>optional</id> |
||||
<active>true</active> |
||||
<protocol>http</protocol> |
||||
<username>proxyuser</username> |
||||
<password>proxypass</password> |
||||
<host>proxy.host.net</host> |
||||
<port>80</port> |
||||
<nonProxyHosts>local.net|some.host.com</nonProxyHosts> |
||||
</proxy> |
||||
--> |
||||
</proxies> |
||||
|
||||
<!-- servers |
||||
| This is a list of authentication profiles, keyed by the server-id used within the system. |
||||
| Authentication profiles can be used whenever maven must make a connection to a remote server. |
||||
|--> |
||||
<servers> |
||||
<!-- server |
||||
| Specifies the authentication information to use when connecting to a particular server, identified by |
||||
| a unique name within the system (referred to by the 'id' attribute below). |
||||
| |
||||
| NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are |
||||
| used together. |
||||
| |
||||
<server> |
||||
<id>deploymentRepo</id> |
||||
<username>repouser</username> |
||||
<password>repopwd</password> |
||||
</server> |
||||
--> |
||||
|
||||
<!-- Another sample, using keys to authenticate. |
||||
<server> |
||||
<id>siteServer</id> |
||||
<privateKey>/path/to/private/key</privateKey> |
||||
<passphrase>optional; leave empty if not used.</passphrase> |
||||
</server> |
||||
--> |
||||
</servers> |
||||
|
||||
<!-- mirrors |
||||
| This is a list of mirrors to be used in downloading artifacts from remote repositories. |
||||
| |
||||
| It works like this: a POM may declare a repository to use in resolving certain artifacts. |
||||
| However, this repository may have problems with heavy traffic at times, so people have mirrored |
||||
| it to several places. |
||||
| |
||||
| That repository definition will have a unique id, so we can create a mirror reference for that |
||||
| repository, to be used as an alternate download site. The mirror site will be the preferred |
||||
| server for that repository. |
||||
|--> |
||||
<mirrors> |
||||
<!-- mirror |
||||
| Specifies a repository mirror site to use instead of a given repository. The repository that |
||||
| this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used |
||||
| for inheritance and direct lookup purposes, and must be unique across the set of mirrors. |
||||
| |
||||
<mirror> |
||||
<id>mirrorId</id> |
||||
<mirrorOf>repositoryId</mirrorOf> |
||||
<name>Human Readable Name for this Mirror.</name> |
||||
<url>http://my.repository.com/repo/path</url> |
||||
</mirror> |
||||
--> |
||||
<mirror> |
||||
<id>nexus-aliyun</id> |
||||
<mirrorOf>central</mirrorOf> |
||||
<name>Nexus aliyun</name> |
||||
<url>http://maven.aliyun.com/nexus/content/groups/public</url> |
||||
</mirror> |
||||
</mirrors> |
||||
|
||||
<!-- profiles |
||||
| This is a list of profiles which can be activated in a variety of ways, and which can modify |
||||
| the build process. Profiles provided in the settings.xml are intended to provide local machine- |
||||
| specific paths and repository locations which allow the build to work in the local environment. |
||||
| |
||||
| For example, if you have an integration testing plugin - like cactus - that needs to know where |
||||
| your Tomcat instance is installed, you can provide a variable here such that the variable is |
||||
| dereferenced during the build process to configure the cactus plugin. |
||||
| |
||||
| As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles |
||||
| section of this document (settings.xml) - will be discussed later. Another way essentially |
||||
| relies on the detection of a system property, either matching a particular value for the property, |
||||
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a |
||||
| value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. |
||||
| Finally, the list of active profiles can be specified directly from the command line. |
||||
| |
||||
| NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact |
||||
| repositories, plugin repositories, and free-form properties to be used as configuration |
||||
| variables for plugins in the POM. |
||||
| |
||||
|--> |
||||
<profiles> |
||||
<!-- profile |
||||
| Specifies a set of introductions to the build process, to be activated using one or more of the |
||||
| mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/> |
||||
| or the command line, profiles have to have an ID that is unique. |
||||
| |
||||
| An encouraged best practice for profile identification is to use a consistent naming convention |
||||
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. |
||||
| This will make it more intuitive to understand what the set of introduced profiles is attempting |
||||
| to accomplish, particularly when you only have a list of profile id's for debug. |
||||
| |
||||
| This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. |
||||
<profile> |
||||
<id>jdk-1.4</id> |
||||
|
||||
<activation> |
||||
<jdk>1.4</jdk> |
||||
</activation> |
||||
|
||||
<repositories> |
||||
<repository> |
||||
<id>jdk14</id> |
||||
<name>Repository for JDK 1.4 builds</name> |
||||
<url>http://www.myhost.com/maven/jdk14</url> |
||||
<layout>default</layout> |
||||
<snapshotPolicy>always</snapshotPolicy> |
||||
</repository> |
||||
</repositories> |
||||
</profile> |
||||
--> |
||||
|
||||
<!-- |
||||
| Here is another profile, activated by the system property 'target-env' with a value of 'dev', |
||||
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration |
||||
| might hypothetically look like: |
||||
| |
||||
| ... |
||||
| <plugin> |
||||
| <groupId>org.myco.myplugins</groupId> |
||||
| <artifactId>myplugin</artifactId> |
||||
| |
||||
| <configuration> |
||||
| <tomcatLocation>${tomcatPath}</tomcatLocation> |
||||
| </configuration> |
||||
| </plugin> |
||||
| ... |
||||
| |
||||
| NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to |
||||
| anything, you could just leave off the <value/> inside the activation-property. |
||||
| |
||||
<profile> |
||||
<id>env-dev</id> |
||||
|
||||
<activation> |
||||
<property> |
||||
<name>target-env</name> |
||||
<value>dev</value> |
||||
</property> |
||||
</activation> |
||||
|
||||
<properties> |
||||
<tomcatPath>/path/to/tomcat/instance</tomcatPath> |
||||
</properties> |
||||
</profile> |
||||
--> |
||||
</profiles> |
||||
|
||||
<!-- activeProfiles |
||||
| List of profiles that are active for all builds. |
||||
| |
||||
<activeProfiles> |
||||
<activeProfile>alwaysActiveProfile</activeProfile> |
||||
<activeProfile>anotherAlwaysActiveProfile</activeProfile> |
||||
</activeProfiles> |
||||
--> |
||||
</settings> |
||||
@ -1,31 +0,0 @@
|
||||
server { |
||||
listen 8888; |
||||
server_name localhost; |
||||
#charset koi8-r; |
||||
#access_log /var/log/nginx/host.access.log main; |
||||
location / { |
||||
root /opt/easyscheduler_source/escheduler-ui/dist; |
||||
index index.html index.html; |
||||
} |
||||
location /escheduler { |
||||
proxy_pass http://127.0.0.1:12345; |
||||
proxy_set_header Host $host; |
||||
proxy_set_header X-Real-IP $remote_addr; |
||||
proxy_set_header x_real_ipP $remote_addr; |
||||
proxy_set_header remote_addr $remote_addr; |
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; |
||||
proxy_http_version 1.1; |
||||
proxy_connect_timeout 300s; |
||||
proxy_read_timeout 300s; |
||||
proxy_send_timeout 300s; |
||||
proxy_set_header Upgrade $http_upgrade; |
||||
proxy_set_header Connection "upgrade"; |
||||
} |
||||
#error_page 404 /404.html; |
||||
# redirect server error pages to the static page /50x.html |
||||
# |
||||
error_page 500 502 503 504 /50x.html; |
||||
location = /50x.html { |
||||
root /usr/share/nginx/html; |
||||
} |
||||
} |
||||
@ -1,28 +0,0 @@
|
||||
# The number of milliseconds of each tick |
||||
tickTime=2000 |
||||
# The number of ticks that the initial |
||||
# synchronization phase can take |
||||
initLimit=10 |
||||
# The number of ticks that can pass between |
||||
# sending a request and getting an acknowledgement |
||||
syncLimit=5 |
||||
# the directory where the snapshot is stored. |
||||
# do not use /tmp for storage, /tmp here is just |
||||
# example sakes. |
||||
dataDir=/tmp/zookeeper |
||||
# the port at which the clients will connect |
||||
clientPort=2181 |
||||
# the maximum number of client connections. |
||||
# increase this if you need to handle more clients |
||||
#maxClientCnxns=60 |
||||
# |
||||
# Be sure to read the maintenance section of the |
||||
# administrator guide before turning on autopurge. |
||||
# |
||||
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance |
||||
# |
||||
# The number of snapshots to retain in dataDir |
||||
#autopurge.snapRetainCount=3 |
||||
# Purge task interval in hours |
||||
# Set to "0" to disable auto purge feature |
||||
#autopurge.purgeInterval=1 |
||||
@ -1,8 +0,0 @@
|
||||
#!/bin/bash |
||||
|
||||
echo "------ push start -------" |
||||
printenv |
||||
|
||||
docker push $DOCKER_REPO:$version |
||||
|
||||
echo "------ push end -------" |
||||
Loading…
Reference in new issue