docker 安装 datax和datax-web 之 datax-web登录时提示账号或密码错误_docker datax
job_desc
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL,
executor_address
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器地址,本次执行的地址’,
executor_handler
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器任务handler’,
executor_param
varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器任务参数’,
executor_sharding_param
varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器任务分片参数,格式如 1/2’,
executor_fail_retry_count
int DEFAULT ‘0’ COMMENT ‘失败重试次数’,
trigger_time
datetime DEFAULT NULL COMMENT ‘调度-时间’,
trigger_code
int NOT NULL COMMENT ‘调度-结果’,
trigger_msg
text CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci COMMENT ‘调度-日志’,
handle_time
datetime DEFAULT NULL COMMENT ‘执行-时间’,
handle_code
int NOT NULL COMMENT ‘执行-状态’,
handle_msg
text CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci COMMENT ‘执行-日志’,
alarm_status
tinyint NOT NULL DEFAULT ‘0’ COMMENT ‘告警状态:0-默认、1-无需告警、2-告警成功、3-告警失败’,
process_id
varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘datax进程Id’,
max_id
bigint DEFAULT NULL COMMENT ‘增量表max id’,
PRIMARY KEY (id
) USING BTREE,
KEY I_trigger_time
(trigger_time
) USING BTREE,
KEY I_handle_code
(handle_code
) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=130 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/*!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_log
LOCK TABLES job_log
WRITE;
/*!40000 ALTER TABLE job_log
DISABLE KEYS /;
INSERT INTO job_log
VALUES (126,1,8,‘aoa_attachment_list’,‘10.68.12.104:9999’,‘executorJobHandler’,‘’,NULL,0,‘2023-04-26 16:18:09’,500,‘任务触发类型:手动触发
调度机器:10.68.12.104
执行器-注册方式:自动注册
执行器-地址列表:[10.68.12.104:9999]
路由策略:随机
阻塞处理策略:丢弃后续调度
任务超时时间:0
失败重试次数:0
<span style=“color:#00c0ef;” > >>>>>>>>>>>触发调度<<<<<<<<<<<
触发调度:
address:10.68.12.104:9999
code:500
msg:glueType[DATAX] is not valid.’,NULL,0,NULL,1,NULL,NULL),(127,1,8,‘aoa_attachment_list’,‘10.68.12.104:9999’,‘executorJobHandler’,‘’,NULL,0,‘2023-04-27 09:22:14’,500,‘任务触发类型:手动触发
调度机器:10.68.12.104
执行器-注册方式:自动注册
执行器-地址列表:[10.68.12.104:9999]
路由策略:随机
阻塞处理策略:丢弃后续调度
任务超时时间:0
失败重试次数:0
<span style=“color:#00c0ef;” > >>>>>>>>>>>触发调度<<<<<<<<<<<
触发调度:
address:10.68.12.104:9999
code:500
msg:glueType[DATAX] is not valid.’,NULL,0,NULL,1,NULL,NULL),(128,1,8,‘aoa_attachment_list’,‘10.68.12.104:9999’,‘executorJobHandler’,‘’,NULL,0,‘2023-04-27 09:31:03’,500,‘任务触发类型:手动触发
调度机器:10.68.12.104
执行器-注册方式:自动注册
执行器-地址列表:[10.68.12.104:9999]
路由策略:随机
阻塞处理策略:丢弃后续调度
任务超时时间:0
失败重试次数:0
<span style=“color:#00c0ef;” > >>>>>>>>>>>触发调度<<<<<<<<<<<
触发调度:
address:10.68.12.104:9999
code:500
msg:glueType[DATAX] is not valid.’,NULL,0,NULL,1,NULL,NULL),(129,1,8,‘aoa_attachment_list’,‘10.68.12.104:9999’,‘executorJobHandler’,‘’,NULL,0,‘2023-04-27 10:53:44’,500,‘任务触发类型:手动触发
调度机器:172.17.0.11
执行器-注册方式:自动注册
执行器-地址列表:[10.68.12.104:9999, 172.17.0.11:9999]
路由策略:随机
阻塞处理策略:丢弃后续调度
任务超时时间:0
失败重试次数:0
<span style=“color:#00c0ef;” > >>>>>>>>>>>触发调度<<<<<<<<<<<
触发调度:
address:10.68.12.104:9999
code:500
msg:glueType[DATAX] is not valid.’,NULL,0,NULL,1,NULL,NULL);
/!40000 ALTER TABLE job_log
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_log_report
DROP TABLE IF EXISTS job_log_report
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 /;
CREATE TABLE job_log_report
(
id
int NOT NULL AUTO_INCREMENT,
trigger_day
datetime DEFAULT NULL COMMENT ‘调度-时间’,
running_count
int NOT NULL DEFAULT ‘0’ COMMENT ‘运行中-日志数量’,
suc_count
int NOT NULL DEFAULT ‘0’ COMMENT ‘执行成功-日志数量’,
fail_count
int NOT NULL DEFAULT ‘0’ COMMENT ‘执行失败-日志数量’,
PRIMARY KEY (id
) USING BTREE,
UNIQUE KEY i_trigger_day
(trigger_day
) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=32 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_log_report
LOCK TABLES job_log_report
WRITE;
/*!40000 ALTER TABLE job_log_report
DISABLE KEYS /;
INSERT INTO job_log_report
VALUES (20,‘2019-12-07 00:00:00’,0,0,0),(21,‘2019-12-10 00:00:00’,77,52,23),(22,‘2019-12-11 00:00:00’,9,2,11),(23,‘2019-12-13 00:00:00’,9,48,74),(24,‘2019-12-12 00:00:00’,10,8,30),(25,‘2019-12-14 00:00:00’,78,45,66),(26,‘2019-12-15 00:00:00’,24,76,9),(27,‘2019-12-16 00:00:00’,23,85,10),(28,‘2023-04-26 00:00:00’,0,0,1),(29,‘2023-04-25 00:00:00’,0,0,0),(30,‘2023-04-24 00:00:00’,0,0,0),(31,‘2023-04-27 00:00:00’,0,0,3);
/!40000 ALTER TABLE job_log_report
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_logglue
DROP TABLE IF EXISTS job_logglue
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 /;
CREATE TABLE job_logglue
(
id
int NOT NULL AUTO_INCREMENT,
job_id
int NOT NULL COMMENT ‘任务,主键ID’,
glue_type
varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘GLUE类型’,
glue_source
mediumtext CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci COMMENT ‘GLUE源代码’,
glue_remark
varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT ‘GLUE备注’,
add_time
datetime DEFAULT NULL,
update_time
datetime DEFAULT NULL,
PRIMARY KEY (id
) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_logglue
LOCK TABLES job_logglue
WRITE;
/*!40000 ALTER TABLE job_logglue
DISABLE KEYS /;
/!40000 ALTER TABLE job_logglue
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_permission
DROP TABLE IF EXISTS job_permission
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 /;
CREATE TABLE job_permission
(
id
int NOT NULL AUTO_INCREMENT COMMENT ‘主键’,
name
varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT ‘权限名’,
description
varchar(11) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘权限描述’,
url
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL,
pid
int DEFAULT NULL,
PRIMARY KEY (id
) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_permission
LOCK TABLES job_permission
WRITE;
/*!40000 ALTER TABLE job_permission
DISABLE KEYS /;
/!40000 ALTER TABLE job_permission
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_project
DROP TABLE IF EXISTS job_project
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 /;
CREATE TABLE job_project
(
id
int NOT NULL AUTO_INCREMENT COMMENT ‘key’,
name
varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘project name’,
description
varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL,
user_id
int DEFAULT NULL COMMENT ‘creator id’,
flag
tinyint DEFAULT ‘1’ COMMENT ‘0 not available, 1 available’,
create_time
datetime DEFAULT CURRENT_TIMESTAMP COMMENT ‘create time’,
update_time
datetime DEFAULT CURRENT_TIMESTAMP COMMENT ‘update time’,
PRIMARY KEY (id
) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_project
LOCK TABLES job_project
WRITE;
/*!40000 ALTER TABLE job_project
DISABLE KEYS /;
INSERT INTO job_project
VALUES (1,‘study’,‘hahhh’,1,1,‘2023-04-26 10:41:06’,‘2023-04-26 10:41:06’);
/!40000 ALTER TABLE job_project
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_registry
DROP TABLE IF EXISTS job_registry
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 /;
CREATE TABLE job_registry
(
id
int NOT NULL AUTO_INCREMENT,
registry_group
varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL,
registry_key
varchar(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL,
registry_value
varchar(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL,
cpu_usage
double DEFAULT NULL,
memory_usage
double DEFAULT NULL,
load_average
double DEFAULT NULL,
update_time
datetime DEFAULT NULL,
PRIMARY KEY (id
) USING BTREE,
KEY i_g_k_v
(registry_group
,registry_key
,registry_value
) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=33 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci ROW_FORMAT=DYNAMIC;
/!40101 SET character_set_client = @saved_cs_client */;
–
– Dumping data for table job_registry
LOCK TABLES job_registry
WRITE;
/*!40000 ALTER TABLE job_registry
DISABLE KEYS /;
INSERT INTO job_registry
VALUES (30,‘EXECUTOR’,‘datax-executor’,‘10.68.12.104:9999’,9.58,73.98,-1,‘2023-04-27 11:46:43’),(32,‘EXECUTOR’,‘datax-executor’,‘172.17.0.10:9999’,1.12,89,0,‘2023-04-27 11:46:51’);
/!40000 ALTER TABLE job_registry
ENABLE KEYS */;
UNLOCK TABLES;
–
– Table structure for table job_template
DROP TABLE IF EXISTS job_template
;
/*!40101 SET @saved_cs_client = @@character_set_client /;
/!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE job_template
(
id
int NOT NULL AUTO_INCREMENT,
job_group
int NOT NULL COMMENT ‘执行器主键ID’,
job_cron
varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL COMMENT ‘任务执行CRON’,
job_desc
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL,
add_time
datetime DEFAULT NULL,
update_time
datetime DEFAULT NULL,
user_id
int NOT NULL COMMENT ‘修改用户’,
alarm_email
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘报警邮件’,
executor_route_strategy
varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器路由策略’,
executor_handler
varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器任务handler’,
executor_param
varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘执行器参数’,
executor_block_strategy
varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci DEFAULT NULL COMMENT ‘阻塞处理策略’,
executor_timeout
int NOT NULL DEFAULT ‘0’ COMMENT ‘任务执行超时时间,单位秒’,
自我介绍一下,小编13年上海交大毕业,曾经在小公司待过,也去过华为、OPPO等大厂,18年进入阿里一直到现在。
深知大多数网络安全工程师,想要提升技能,往往是自己摸索成长,但自己不成体系的自学效果低效又漫长,而且极易碰到天花板技术停滞不前!
因此收集整理了一份《2024年网络安全全套学习资料》,初衷也很简单,就是希望能够帮助到想自学提升又不知道该从何学起的朋友。
既有适合小白学习的零基础资料,也有适合3年以上经验的小伙伴深入学习提升的进阶课程,基本涵盖了95%以上网络安全知识点,真正体系化!
由于文件比较大,这里只是将部分目录大纲截图出来,每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频,并且后续会持续更新
如果你觉得这些内容对你有帮助,可以添加VX:vip204888 (备注网络安全获取)
写在最后
在结束之际,我想重申的是,学习并非如攀登险峻高峰,而是如滴水穿石般的持久累积。尤其当我们步入工作岗位之后,持之以恒的学习变得愈发不易,如同在茫茫大海中独自划舟,稍有松懈便可能被巨浪吞噬。然而,对于我们程序员而言,学习是生存之本,是我们在激烈市场竞争中立于不败之地的关键。一旦停止学习,我们便如同逆水行舟,不进则退,终将被时代的洪流所淘汰。因此,不断汲取新知识,不仅是对自己的提升,更是对自己的一份珍贵投资。让我们不断磨砺自己,与时代共同进步,书写属于我们的辉煌篇章。
需要完整版PDF学习资源私我
一个人可以走的很快,但一群人才能走的更远。不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎扫码加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!
自己的提升,更是对自己的一份珍贵投资。让我们不断磨砺自己,与时代共同进步,书写属于我们的辉煌篇章。**
需要完整版PDF学习资源私我
一个人可以走的很快,但一群人才能走的更远。不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎扫码加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!
[外链图片转存中…(img-FyZWAjvg-1712583873935)]
更多推荐
所有评论(0)