Apache Druid元数据从Derby转成MySQL

Druid元数据从Derby转成MySQL

默认情况下使用的是Derby数据库，Derby非常小巧，核心部分derby.jar只有2M，所以既可以做为单独的数据库服务器使用，也可以内嵌在应用程序中使用,但是Druid部署集群的模式下，或者Druid的单机规模数据很多的情况，这里就不适合使用Derby,测试情况下倒是挺合适的。

本文档就是把已经运行一段时间的Druid单机服务的元数据迁移到MySQL上，同时使用MySql当成元数据库

场景：可以参考Druid0.12.0版本单机最简安装

数据也是真实的，运行了几个小时，共有60250160条数据

把元数据导出到CSV文件中

从DerBy数据库中导出数据，请参考 Druid元数据从Derby导出到CSV

安装MySQL数据库

安装MySQL数据库，可以参考Centos7.2安装Mysql5.7及配置

配置好，可以允许远程登录 MySQL中的一些问题可以参考 在Linux下使用Mysql常见的问题集锦

创建一个数据库(demo)

CREATE USER 'demo'@'%' IDENTIFIED BY 'demo';

CREATE DATABASE demo DEFAULT CHARACTER SET utf8;

GRANT ALL PRIVILEGES ON *.* TO 'demo'@'%' WITH GRANT OPTION;

commit;

配置Druid的元数据管理信息

修改配置

vim DRUID_HOME/conf-quickstart/druid/_common/common.runtime.properties

druid.extensions.loadList=["druid-kafka-indexing-service","mysql-metadata-storage"]

# For Derby server on your Druid Coordinator (only viable in a cluster with a single Coordinator, no fail-over):
#druid.metadata.storage.type=derby
#druid.metadata.storage.connector.connectURI=jdbc:derby://localhost:1527/var/druid/metadata.db;create=true
#druid.metadata.storage.connector.host=localhost
#druid.metadata.storage.connector.port=1527

# For MySQL:
druid.metadata.storage.type=mysql
druid.metadata.storage.connector.connectURI=jdbc:mysql://192.168.1.91:3306/demo
druid.metadata.storage.connector.user=demo
druid.metadata.storage.connector.password=demo

下载MySQL的扩展包及的驱动包（默认当前版本没有MySQL的扩展包,到后面的版本默认就有MySQL扩展的包了）

cd /opt/install

wget http://static.druid.io/artifacts/releases/mysql-metadata-storage-0.12.0.tar.gz

tar -zxf mysql-metadata-storage-0.12.0.tar.gz -C druid-0.12.0/extensions/

ll druid-0.12.0/extensions/mysql-metadata-storage

-rw-r--r-- 1 501 games 983911 Apr 21  2016 mysql-connector-java-5.1.38.jar
-rw-r--r-- 1 501 games  10476 Mar  8  2018 mysql-metadata-storage-0.12.0.jar

上传从DerBy导出的CSV文件

默认上传到/var/lib/mysql-files/目录下，这样MySQL才有权限执行加载这个目录下的文件

[root@itdeer ~]# ll /var/lib/mysql-files/csv
total 116
-rw-r--r-- 1 root root     0 Jun 12 17:59 druid_config.csv
-rw-r--r-- 1 root root     0 Jun 12 17:59 druid_config_raw.csv
-rw-r--r-- 1 root root   172 Jun 12 17:59 druid_dataSource.csv
-rw-r--r-- 1 root root   246 Jun 12 17:59 druid_dataSource_raw.csv
-rw-r--r-- 1 root root   142 Jun 12 17:59 druid_rules.csv
-rw-r--r-- 1 root root   203 Jun 12 17:59 druid_rules_raw.csv
-rw-r--r-- 1 root root 32773 Jun 12 17:59 druid_segments.csv
-rw-r--r-- 1 root root 54426 Jun 12 17:59 druid_segments_raw.csv
-rw-r--r-- 1 root root  1654 Jun 12 17:59 druid_supervisors.csv
-rw-r--r-- 1 root root  2878 Jun 12 17:59 druid_supervisors_raw.csv

在导入数据之前需要有表

默认状态下Druid只要运行起来之后所有的元数据表都已经存在了。这里可以先运行一下Druid的coordinator服务，自动创建一下元数据表结构


或者使用一下命令创建也是可以的

/*
Navicat Premium Data Transfer

Source Server         : node1
Source Server Type    : MySQL
Source Server Version : 50721
Source Host           : 192.168.1.91:3306
Source Schema         : druid

Target Server Type    : MySQL
Target Server Version : 50721
File Encoding         : 65001

Date: 15/06/2020 15:34:26
*/

SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;

-- ----------------------------
-- Table structure for druid_audit
-- ----------------------------
DROP TABLE IF EXISTS `druid_audit`;
CREATE TABLE `druid_audit`  (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`audit_key` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`type` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`author` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`comment` varchar(2048) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_audit_key_time`(`audit_key`, `created_date`) USING BTREE,
INDEX `idx_druid_audit_type_time`(`type`, `created_date`) USING BTREE,
INDEX `idx_druid_audit_audit_time`(`created_date`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 51 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_config
-- ----------------------------
DROP TABLE IF EXISTS `druid_config`;
CREATE TABLE `druid_config`  (
`name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`name`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_dataSource
-- ----------------------------
DROP TABLE IF EXISTS `druid_dataSource`;
CREATE TABLE `druid_dataSource`  (
`dataSource` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`commit_metadata_payload` longblob NOT NULL,
`commit_metadata_sha1` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
PRIMARY KEY (`dataSource`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_pendingSegments
-- ----------------------------
DROP TABLE IF EXISTS `druid_pendingSegments`;
CREATE TABLE `druid_pendingSegments`  (
`id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`dataSource` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`start` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`end` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`sequence_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`sequence_prev_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`sequence_name_prev_id_sha1` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `sequence_name_prev_id_sha1`(`sequence_name_prev_id_sha1`) USING BTREE,
INDEX `idx_druid_pendingSegments_datasource_end`(`dataSource`, `end`) USING BTREE,
INDEX `idx_druid_pendingSegments_datasource_sequence`(`dataSource`, `sequence_name`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_rules
-- ----------------------------
DROP TABLE IF EXISTS `druid_rules`;
CREATE TABLE `druid_rules`  (
`id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`dataSource` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`version` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_rules_datasource`(`dataSource`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_segments
-- ----------------------------
DROP TABLE IF EXISTS `druid_segments`;
CREATE TABLE `druid_segments`  (
`id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`dataSource` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`start` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`end` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`partitioned` tinyint(1) NOT NULL,
`version` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`used` tinyint(1) NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_segments_used`(`used`) USING BTREE,
INDEX `idx_druid_segments_datasource_used_end`(`dataSource`, `used`, `end`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_supervisors
-- ----------------------------
DROP TABLE IF EXISTS `druid_supervisors`;
CREATE TABLE `druid_supervisors`  (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`spec_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`payload` longblob NOT NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_supervisors_spec_id`(`spec_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_tasklocks
-- ----------------------------
DROP TABLE IF EXISTS `druid_tasklocks`;
CREATE TABLE `druid_tasklocks`  (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`task_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
`lock_payload` longblob NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_tasklocks_task_id`(`task_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 55 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_tasklogs
-- ----------------------------
DROP TABLE IF EXISTS `druid_tasklogs`;
CREATE TABLE `druid_tasklogs`  (
`id` bigint(20) NOT NULL AUTO_INCREMENT,
`task_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,
`log_payload` longblob NULL,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_tasklogs_task_id`(`task_id`) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

-- ----------------------------
-- Table structure for druid_tasks
-- ----------------------------
DROP TABLE IF EXISTS `druid_tasks`;
CREATE TABLE `druid_tasks`  (
`id` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`created_date` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
`datasource` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`payload` longblob NOT NULL,
`status_payload` longblob NOT NULL,
`active` tinyint(1) NOT NULL DEFAULT 0,
PRIMARY KEY (`id`) USING BTREE,
INDEX `idx_druid_tasks_active_created_date`(`active`, `created_date`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic;

SET FOREIGN_KEY_CHECKS = 1;

导入文件

mysql -u demo -p 

mysql> LOAD DATA INFILE '/var/lib/mysql-files/csv/druid_segments.csv' INTO TABLE druid_segments FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '\"' (id,dataSource,created_date,start,end,partitioned,version,used,payload); SHOW WARNINGS;
Query OK, 41 rows affected (0.01 sec)
Records: 41  Deleted: 0  Skipped: 0  Warnings: 0

Empty set (0.00 sec)

mysql> LOAD DATA INFILE '/var/lib/mysql-files/csv/druid_rules.csv' INTO TABLE druid_rules FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '\"' (id,dataSource,version,payload); SHOW WARNINGS;
Query OK, 1 row affected (0.00 sec)
Records: 1  Deleted: 0  Skipped: 0  Warnings: 0

Empty set (0.00 sec)

mysql> LOAD DATA INFILE '/var/lib/mysql-files/csv/druid_config.csv' INTO TABLE druid_config FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '\"' (name,payload); SHOW WARNINGS;
Query OK, 0 rows affected (0.00 sec)
Records: 0  Deleted: 0  Skipped: 0  Warnings: 0

Empty set (0.00 sec)

mysql> LOAD DATA INFILE '/var/lib/mysql-files/csv/druid_dataSource.csv' INTO TABLE druid_dataSource FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '\"' (dataSource,created_date,commit_metadata_payload,commit_metadata_sha1); SHOW WARNINGS;
Query OK, 1 row affected (0.01 sec)
Records: 1  Deleted: 0  Skipped: 0  Warnings: 0

Empty set (0.00 sec)

mysql> LOAD DATA INFILE '/var/lib/mysql-files/csv/druid_supervisors.csv' INTO TABLE druid_supervisors FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '\"' (id,spec_id,created_date,payload); SHOW WARNINGS;
Query OK, 2 rows affected (0.00 sec)
Records: 2  Deleted: 0  Skipped: 0  Warnings: 0

Empty set (0.00 sec)

查看结果

访问界面(http://IP:8081) Druid DataDource Console界面(数据源和之前是一样的)

20206122315

查询数据(数据条数也是正确的)

202061223118

至此把Druid的元数据管理从DerBy数据库替换成MySQL数据库完成

©著作权归作者所有,转载或内容合作请联系作者
  • 人面猴
    序言：七十年代末，一起剥皮案震惊了整个滨河市，随后出现的几起案子，更是在滨河造成了极大的恐慌，老刑警刘岩，带你破解...
    沈念sama阅读 213,711评论 6赞 493
  • 死咒
    序言：滨河连续发生了三起死亡事件，死亡现场离奇诡异，居然都是意外死亡，警方通过查阅死者的电脑和手机，发现死者居然都...
    沈念sama阅读 91,079评论 3赞 387
  • 救了他两次的神仙让他今天三更去死
    文/潘晓璐 我一进店门，熙熙楼的掌柜王于贵愁眉苦脸地迎上来，“玉大人，你说我怎么就摊上这事。” “怎么了？”我有些...
    开封第一讲书人阅读 159,194评论 0赞 349
  • 道士缉凶录：失踪的卖姜人
    文/不坏的土叔 我叫张陵，是天一观的道长。 经常有香客问我，道长，这世上最难降的妖魔是什么？ 我笑而不...
    开封第一讲书人阅读 57,089评论 1赞 286
  • 港岛之恋（遗憾婚礼）
    正文 为了忘掉前任，我火速办了婚礼，结果婚礼上，老公的妹妹穿的比我还像新娘。我一直安慰自己，他们只是感情好，可当我...
    茶点故事阅读 66,197评论 6赞 385
  • 恶毒庶女顶嫁案：这布局不是一般人想出来的
    文/花漫 我一把揭开白布。 她就那样静静地躺着，像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上，一...
    开封第一讲书人阅读 50,306评论 1赞 292
  • 城市分裂传说
    那天，我揣着相机与录音，去河边找鬼。 笑死，一个胖子当着我的面吹牛，可吹牛的内容都是我干的。 我是一名探鬼主播，决...
    沈念sama阅读 39,338评论 3赞 412
  • 双鸳鸯连环套：你想象不到人心有多黑
    文/苍兰香墨 我猛地睁开眼，长吁一口气：“原来是场噩梦啊……” “哼！你这毒妇竟也来了？” 一声冷哼从身侧响起，我...
    开封第一讲书人阅读 38,119评论 0赞 269
  • 万荣杀人案实录
    序言：老挝万荣一对情侣失踪，失踪者是张志新（化名）和其女友刘颖，没想到半个月后，有当地人在树林里发现了一具尸体，经...
    沈念sama阅读 44,541评论 1赞 306
  • 护林员之死
    正文 独居荒郊野岭守林人离奇死亡，尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 36,846评论 2赞 328
  • 白月光启示录
    正文 我和宋清朗相恋三年，在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 39,014评论 1赞 341
  • 活死人
    序言：一个原本活蹦乱跳的男人离奇死亡，死状恐怖，灵堂内的尸体忽然破棺而出，到底是诈尸还是另有隐情，我是刑警宁泽，带...
    沈念sama阅读 34,694评论 4赞 337
  • 日本核电站爆炸内幕
    正文 年R本政府宣布，位于F岛的核电站，受9级特大地震影响，放射性物质发生泄漏。R本人自食恶果不足惜，却给世界环境...
    茶点故事阅读 40,322评论 3赞 318
  • 男人毒药：我在死后第九天来索命
    文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹，春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 31,026评论 0赞 21
  • 一桩弑父案，背后竟有这般阴谋
    文/苍兰香墨 我抬头看了看天上的太阳。三九已至，却和暖如春，着一层夹袄步出监牢的瞬间，已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 32,257评论 1赞 267
  • 情欲美人皮
    我被黑心中介骗来泰国打工， 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留，地道东北人。 一个月前我还...
    沈念sama阅读 46,863评论 2赞 365
  • 代替公主和亲
    正文 我出身青楼，却偏偏与公主长得像，于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子，可洞房花烛夜当晚...
    茶点故事阅读 43,895评论 2赞 351