1. Toy模板网首页
  2. > Toy博客

Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）

7月前 作者：Long long ago. 分类：Toy博客 阅读(32) 违法举报

这篇具有很好参考价值的文章主要介绍了Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）。希望对大家有所帮助。如果存在错误或未考虑完全的地方，请大家不吝赐教，您也可以点击"举报违法"按钮提交疑问。

官网

https://www.kafka-eagle.org/

下载解压

这里使用的是2.0.8

创建mysql数据库

创建名为ke数据库,新版本会自动创建，不会创建的话，自己手动创建，不然会报查不到相关表信息错误

SET NAMES utf8;
SET FOREIGN_KEY_CHECKS = 0;
 
-- ----------------------------
-- Table structure for ke_alarm_clusters
-- ----------------------------
DROP TABLE IF EXISTS `ke_alarm_clusters`;
CREATE TABLE `ke_alarm_clusters`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `type` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `server` text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `alarm_group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `alarm_times` int NULL DEFAULT NULL,
  `alarm_max_times` int NULL DEFAULT NULL,
  `alarm_level` varchar(4) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `is_normal` varchar(2) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'Y',
  `is_enable` varchar(2) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'Y',
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `modify` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_alarm_clusters
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_alarm_config
-- ----------------------------
DROP TABLE IF EXISTS `ke_alarm_config`;
CREATE TABLE `ke_alarm_config`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `alarm_group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `alarm_type` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `alarm_url` text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `http_method` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `alarm_address` text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `modify` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`cluster`, `alarm_group`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_alarm_config
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_alarm_consumer
-- ----------------------------
DROP TABLE IF EXISTS `ke_alarm_consumer`;
CREATE TABLE `ke_alarm_consumer`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `topic` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `lag` bigint NULL DEFAULT NULL,
  `alarm_group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `alarm_times` int NULL DEFAULT NULL,
  `alarm_max_times` int NULL DEFAULT NULL,
  `alarm_level` varchar(4) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `is_normal` varchar(2) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'Y',
  `is_enable` varchar(2) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'Y',
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `modify` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_alarm_consumer
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_alarm_crontab
-- ----------------------------
DROP TABLE IF EXISTS `ke_alarm_crontab`;
CREATE TABLE `ke_alarm_crontab`  (
  `id` bigint NOT NULL,
  `type` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `crontab` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `is_enable` varchar(2) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'Y',
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `modify` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`id`, `type`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_alarm_crontab
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_connect_config
-- ----------------------------
DROP TABLE IF EXISTS `ke_connect_config`;
CREATE TABLE `ke_connect_config`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `connect_uri` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `version` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `alive` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `modify` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_connect_config
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_consumer_bscreen
-- ----------------------------
DROP TABLE IF EXISTS `ke_consumer_bscreen`;
CREATE TABLE `ke_consumer_bscreen`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `topic` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `logsize` bigint NULL DEFAULT NULL,
  `difflogsize` bigint NULL DEFAULT NULL,
  `offsets` bigint NULL DEFAULT NULL,
  `diffoffsets` bigint NULL DEFAULT NULL,
  `lag` bigint NULL DEFAULT NULL,
  `timespan` bigint NULL DEFAULT NULL,
  `tm` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  INDEX `idx_timespan`(`timespan`) USING BTREE,
  INDEX `idx_tm_cluster_diffoffsets`(`tm`, `cluster`, `diffoffsets`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_consumer_bscreen
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_consumer_group
-- ----------------------------
DROP TABLE IF EXISTS `ke_consumer_group`;
CREATE TABLE `ke_consumer_group`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `topic` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `status` int NULL DEFAULT NULL,
  PRIMARY KEY (`cluster`, `group`, `topic`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_consumer_group
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_consumer_group_summary
-- ----------------------------
DROP TABLE IF EXISTS `ke_consumer_group_summary`;
CREATE TABLE `ke_consumer_group_summary`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `group` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `topic_number` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `coordinator` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `active_topic` int NULL DEFAULT NULL,
  `active_thread_total` int NULL DEFAULT NULL,
  PRIMARY KEY (`cluster`, `group`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_consumer_group_summary
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_logsize
-- ----------------------------
DROP TABLE IF EXISTS `ke_logsize`;
CREATE TABLE `ke_logsize`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `topic` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `logsize` bigint NULL DEFAULT NULL,
  `diffval` bigint NULL DEFAULT NULL,
  `timespan` bigint NULL DEFAULT NULL,
  `tm` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  INDEX `idx_timespan`(`timespan`) USING BTREE,
  INDEX `idx_tm_topic`(`tm`, `topic`) USING BTREE,
  INDEX `idx_tm_cluster_diffval`(`tm`, `cluster`, `diffval`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_logsize
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_metrics
-- ----------------------------
DROP TABLE IF EXISTS `ke_metrics`;
CREATE TABLE `ke_metrics`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `broker` text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `type` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `key` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `value` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `timespan` bigint NULL DEFAULT NULL,
  `tm` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_metrics
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_metrics_offline
-- ----------------------------
DROP TABLE IF EXISTS `ke_metrics_offline`;
CREATE TABLE `ke_metrics_offline`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `key` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `one` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `mean` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `five` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `fifteen` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`cluster`, `key`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_metrics_offline
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_p_role
-- ----------------------------
DROP TABLE IF EXISTS `ke_p_role`;
CREATE TABLE `ke_p_role`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `name` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT 'role name',
  `seq` tinyint NOT NULL COMMENT 'rank',
  `description` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT 'role describe',
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 4 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_p_role
-- ----------------------------
INSERT INTO `ke_p_role` VALUES (1, 'Administrator', 1, 'Have all permissions');
INSERT INTO `ke_p_role` VALUES (2, 'Devs', 2, 'Own add or delete');
INSERT INTO `ke_p_role` VALUES (3, 'Tourist', 3, 'Only viewer');
 
-- ----------------------------
-- Table structure for ke_resources
-- ----------------------------
DROP TABLE IF EXISTS `ke_resources`;
CREATE TABLE `ke_resources`  (
  `resource_id` bigint NOT NULL AUTO_INCREMENT,
  `name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL COMMENT 'resource name',
  `url` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `parent_id` int NOT NULL,
  PRIMARY KEY (`resource_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 25 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_resources
-- ----------------------------
INSERT INTO `ke_resources` VALUES (1, 'System', '/system', -1);
INSERT INTO `ke_resources` VALUES (2, 'User', '/system/user', 1);
INSERT INTO `ke_resources` VALUES (3, 'Role', '/system/role', 1);
INSERT INTO `ke_resources` VALUES (4, 'Resource', '/system/resource', 1);
INSERT INTO `ke_resources` VALUES (5, 'Notice', '/system/notice', 1);
INSERT INTO `ke_resources` VALUES (6, 'Topic', '/topic', -1);
INSERT INTO `ke_resources` VALUES (7, 'Message', '/topic/message', 6);
INSERT INTO `ke_resources` VALUES (8, 'Create', '/topic/create', 6);
INSERT INTO `ke_resources` VALUES (9, 'Alarm', '/alarm', -1);
INSERT INTO `ke_resources` VALUES (10, 'Add', '/alarm/add', 9);
INSERT INTO `ke_resources` VALUES (11, 'Modify', '/alarm/modify', 9);
INSERT INTO `ke_resources` VALUES (12, 'Cluster', '/cluster', -1);
INSERT INTO `ke_resources` VALUES (13, 'ZkCli', '/cluster/zkcli', 12);
INSERT INTO `ke_resources` VALUES (14, 'UserDelete', '/system/user/delete', 1);
INSERT INTO `ke_resources` VALUES (15, 'UserModify', '/system/user/modify', 1);
INSERT INTO `ke_resources` VALUES (16, 'Mock', '/topic/mock', 6);
INSERT INTO `ke_resources` VALUES (18, 'Create', '/alarm/create', 9);
INSERT INTO `ke_resources` VALUES (19, 'History', '/alarm/history', 9);
INSERT INTO `ke_resources` VALUES (20, 'Manager', '/topic/manager', 6);
INSERT INTO `ke_resources` VALUES (21, 'PasswdReset', '/system/user/reset', 1);
INSERT INTO `ke_resources` VALUES (22, 'Config', '/alarm/config', 9);
INSERT INTO `ke_resources` VALUES (23, 'List', '/alarm/list', 9);
INSERT INTO `ke_resources` VALUES (24, 'Hub', '/topic/hub', 6);
 
-- ----------------------------
-- Table structure for ke_role_resource
-- ----------------------------
DROP TABLE IF EXISTS `ke_role_resource`;
CREATE TABLE `ke_role_resource`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `role_id` int NOT NULL,
  `resource_id` int NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 26 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_role_resource
-- ----------------------------
INSERT INTO `ke_role_resource` VALUES (1, 1, 1);
INSERT INTO `ke_role_resource` VALUES (2, 1, 2);
INSERT INTO `ke_role_resource` VALUES (3, 1, 3);
INSERT INTO `ke_role_resource` VALUES (4, 1, 4);
INSERT INTO `ke_role_resource` VALUES (5, 1, 5);
INSERT INTO `ke_role_resource` VALUES (6, 1, 7);
INSERT INTO `ke_role_resource` VALUES (7, 1, 8);
INSERT INTO `ke_role_resource` VALUES (8, 1, 10);
INSERT INTO `ke_role_resource` VALUES (9, 1, 11);
INSERT INTO `ke_role_resource` VALUES (10, 1, 13);
INSERT INTO `ke_role_resource` VALUES (11, 2, 7);
INSERT INTO `ke_role_resource` VALUES (12, 2, 8);
INSERT INTO `ke_role_resource` VALUES (13, 2, 13);
INSERT INTO `ke_role_resource` VALUES (14, 2, 10);
INSERT INTO `ke_role_resource` VALUES (15, 2, 11);
INSERT INTO `ke_role_resource` VALUES (16, 1, 14);
INSERT INTO `ke_role_resource` VALUES (17, 1, 15);
INSERT INTO `ke_role_resource` VALUES (18, 1, 16);
INSERT INTO `ke_role_resource` VALUES (19, 1, 18);
INSERT INTO `ke_role_resource` VALUES (20, 1, 19);
INSERT INTO `ke_role_resource` VALUES (21, 1, 20);
INSERT INTO `ke_role_resource` VALUES (22, 1, 21);
INSERT INTO `ke_role_resource` VALUES (23, 1, 22);
INSERT INTO `ke_role_resource` VALUES (24, 1, 23);
INSERT INTO `ke_role_resource` VALUES (25, 1, 24);
 
-- ----------------------------
-- Table structure for ke_sql_history
-- ----------------------------
DROP TABLE IF EXISTS `ke_sql_history`;
CREATE TABLE `ke_sql_history`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `username` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `host` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `ksql` text CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `status` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `spend_time` bigint NULL DEFAULT NULL,
  `created` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  `tm` varchar(16) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_sql_history
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_topic_rank
-- ----------------------------
DROP TABLE IF EXISTS `ke_topic_rank`;
CREATE TABLE `ke_topic_rank`  (
  `cluster` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `topic` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `tkey` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `tvalue` bigint NULL DEFAULT NULL,
  PRIMARY KEY (`cluster`, `topic`, `tkey`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_topic_rank
-- ----------------------------
 
-- ----------------------------
-- Table structure for ke_user_role
-- ----------------------------
DROP TABLE IF EXISTS `ke_user_role`;
CREATE TABLE `ke_user_role`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `user_id` int NOT NULL,
  `role_id` tinyint NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_user_role
-- ----------------------------
INSERT INTO `ke_user_role` VALUES (1, 1, 1);
 
-- ----------------------------
-- Table structure for ke_users
-- ----------------------------
DROP TABLE IF EXISTS `ke_users`;
CREATE TABLE `ke_users`  (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `rtxno` int NOT NULL,
  `username` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `password` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `email` varchar(64) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `realname` varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  PRIMARY KEY (`id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;
 
-- ----------------------------
-- Records of ke_users
-- ----------------------------
INSERT INTO `ke_users` VALUES (1, 1000, 'admin', '123456', 'admin@email.com', 'Administrator');
 
SET FOREIGN_KEY_CHECKS = 1;

配置环境遍历

# kafkaEFAK
export KE_HOME=/usr/local/src/kafka-eagle/kafka-eagle-bin-2.0.8/efak-web-2.0.8
export PATH=$PATH:$KE_HOME/bin

Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）,kafka,分布式
记得source

source /etc/profile.d/my_env.sh

修改配置

vim $KE_HOME/conf/system-config.properties

多余的配置去掉
Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）,kafka,分布式
Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）,kafka,分布式

如果发现启动失败，可能是mysql版本不同，导致连不上数据库，可以看下日志报错，以下配置是5.7版本的

efak.driver=com.mysql.jdbc.Driver
efak.url=jdbc:mysql://hadoop100:3306/ke?useUnicode=true&characterEncoding=UTF-8&serverTimezone=GMT
efak.username=root
efak.password=*****

启动

ke.sh start

初始化账号密码 admin 123456
Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）,kafka,分布式文章来源地址https://www.toymoban.com/news/detail-567069.html

到了这里，关于Kafka入门，mysql5.7 Kafka-Eagle部署（二十五）的文章就介绍完了。如果您还想了解更多内容，请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章，希望大家以后多多支持TOY模板网！

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处： 如若内容造成侵权/违法违规/事实不符，请点击违法举报进行投诉反馈，一经查实，立即删除！

分享到：
领支付宝红包 赞助服务器费用

相关文章

  • 【Kafka】Kafka监控工具Kafka-eagle简介

    Kafka-eagle是一种基于Web的开源管理工具，可以用来监控、管理多个Kafka集群。 下面是使用Docker部署Kafka-eagle的步骤： 下载并安装Docker和Docker Compose。 创建文件夹，例如kafka-eagle，并在其中创建docker-compose.yml文件，将以下配置写入： 在命令行中转到kafka-eagle文件夹中，运行以下命

    2024年02月14日
    浏览(28)
  • Kafka运维监控：Kafka-Eagle安装

    Kafka运维监控：Kafka-Eagle安装

    kafka自身并没有集成监控管理系统，因此对kafka的监控管理比较不便，好在有大量的第三方监控管理系统来使用，常见的有： Kafka Eagle KafkaOffsetMonitor Kafka Manager（雅虎开源的Kafka集群管理器） Kafka Web Console 还有JMX接口自开发监控管理系统 安装包下载地址：http://download.kafka-eag

    2024年02月16日
    浏览(26)
  • 5、kafka监控工具Kafka-Eagle介绍及使用

    5、kafka监控工具Kafka-Eagle介绍及使用

    1、kafka（2.12-3.0.0）介绍、部署及验证、基准测试 2、java调用kafka api 3、kafka重要概念介紹及示例 4、kafka分区、副本介绍及示例 5、kafka监控工具Kafka-Eagle介绍及使用 本文主要介绍了kafka监控工具Kafka-Eagle的使用。 本文依赖：kafka、zookeeper部署完成。 本分分为三个部分介绍，即

    2024年02月09日
    浏览(33)
  • Kafka-Eagle安装及连接成功web端登陆不了问题解决

    Kafka-Eagle安装及连接成功web端登陆不了问题解决

    kafka自身并没有集成监控管理系统，因此对kafka的监控管理比较不便，好在有大量的第三方监控管理系统来使用，常见的有： Kafka Eagle KafkaOffsetMonitor Kafka Manager（雅虎开源的Kafka集群管理器） Kafka Web Console 还有JMX接口自开发监控管理系统 以下是3.1.0版TV页面 Kafka-Eagle安装 安装包

    2024年02月08日
    浏览(36)
  • 上手第一关，手把手教你安装kafka与可视化工具kafka-eagle

    上手第一关，手把手教你安装kafka与可视化工具kafka-eagle

    终于又开新专栏啦（其实是填坑），相信很多同学对kafka都有一定的了解了，我们以前在RabbitMQ的选型中，也提到过两者的对比，那么今天我们就正式开始Kafka的学习吧，老规矩，先来一篇手把手安装教程，因为后续主要是用于自身学习，所以还是以windows的安装为例 📕作者简

    2024年02月08日
    浏览(33)
  • Kafka入门， Kafka-Kraft 模式 部署（二十六）

    Kafka入门， Kafka-Kraft 模式 部署（二十六）

    左图为kafka现有架构，元数据在zookeeper中，运行时动态选举controller,由controller进行kafka集群管理，右图为kraft模式架构（实验性），不再依赖zookeeper集群，而是用三台controller节点代替zookeeper，元数据保存在controller中，由controller直接2进行kafka集群管理 好处： 1、kafka不再依赖外

    2024年02月13日
    浏览(28)

  • 【大数据系列之MySQL】（二十五）：MySQL中的子查询

    子查询：出现在其它语句内部的select语句，称为子查询或内查询，就是嵌套的查询结果集 子查询分类 按子查询出现的位置： select后面：仅仅支持标量子查询 from后面：支持表子查询 where或having后面：标量子查询、列子查询、行子查询 exists后面（相关子查询） 按结果集的行列

    2024年02月13日
    浏览(21)
  • WPF入门教程系列二十五——DataGrid使用示例(2)

    WPF入门教程系列二十五——DataGrid使用示例(2)

    WPF入门教程系列目录 WPF入门教程系列二——Application介绍 WPF入门教程系列三——Application介绍(续) WPF入门教程系列四——Dispatcher介绍 WPF入门教程系列五——Window 介绍 WPF入门教程系列十一——依赖属性（一） WPF入门教程系列十五——WPF中的数据绑定(一)        默认情况下

    2024年02月05日
    浏览(37)
  • CENTOS上的网络安全工具（二十五）SPARK+NetSA Security Tools容器化部署(1)

    CENTOS上的网络安全工具（二十五）SPARK+NetSA Security Tools容器化部署(1)

                 YAF（Yet Another Flowmeter）是作为CERT NetSA安全工具套件的传感器部分存在的，支持输入实时数据流和PCAP文件，解析并输出流数据，或针对特定协议的深包检测元数据。目前，YAF在整个系统的作用如下图所示：         其中Pipeline和SiLK都存在好多年了，用起来也算

    2024年02月11日
    浏览(32)

  • 从零开始学习 Java：简单易懂的入门指南之可变参数及Collections类（二十五）

    在 JDK1.5 之后，如果我们定义一个方法需要接受多个参数，并且多个参数类型一致，我们可以对其简化. 格式： 底层： ​ 其实就是一个数组 好处： ​ 在传递数据的时候，省的我们自己创建数组并添加元素了，JDK底层帮我们自动创建数组并添加元素了 代码演示: 注意： ​

    2024年02月07日
    浏览(31)

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

请作者喝杯咖啡吧~博客赞助

支付宝扫一扫领取红包，优惠每天领

二维码1

领取红包

二维码2

领红包