dm2 start-task报错:sources have not bound?

问题一、

{
    "result": false,
    "msg": "[code=46009:class=dm-master:scope=internal:level=medium] sources [lancer01] have not bound",
    "sources": [
    ]
}

请问这个要怎么解决?

一个worker只能执行一个task?

问题二:下面报的是外键错误?怎么跳过这个报错?而且下面的表我没有同步,不知道为什么会报这个错误

» start-task lancer01-task01.yaml
{
    "result": false,
    "msg": "[code=26005:class=dm-master:scope=internal:level=medium], Message: fail to check synchronization configuration with type: check was failed, please see detail
    	detail: {
		"results": [
			{
				"id": 7,
				"name": "table structure compatibility check",
				"desc": "check compatibility of table structure",
				"state": "fail",
				"errorMsg": "********** table `tlsydb`.`admin_activations` **********\
statement: CREATE TABLE `admin_activations` (\
  `email` varchar(191) NOT NULL,\
  `token` varchar(191) NOT NULL,\
  `used` tinyint(1) NOT NULL DEFAULT '0',\
  `created_at` timestamp NULL DEFAULT NULL,\
  KEY `admin_activations_email_index` (`email`)\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4\
---------- error messages ----------\
information: primary/unique key does not exist\
instruction: please set primary/unique key for the table\
\
********** table `tlsydb`.`role_has_permissions` **********\
statement: CREATE TABLE `role_has_permissions` (\
  `permission_id` int(10) unsigned NOT NULL,\
  `role_id` int(10) unsigned NOT NULL,\
  PRIMARY KEY (`permission_id`,`role_id`),\
  KEY `role_has_permissions_role_id_foreign` (`role_id`),\
  CONSTRAINT `role_has_permissions_permission_id_foreign` FOREIGN KEY (`permission_id`) REFERENCES `permissions` (`id`) ON DELETE CASCADE,\
  CONSTRAINT `role_has_permissions_role_id_foreign` FOREIGN KEY (`role_id`) REFERENCES `roles` (`id`) ON DELETE CASCADE\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci\
---------- warning messages ----------\
information: Foreign Key role_has_permissions_permission_id_foreign is parsed but ignored by TiDB.\
instruction: please ref document: https://github.com/pingcap/docs-cn/blob/master/sql/ddl.md\
\
information: Foreign Key role_has_permissions_role_id_foreign is parsed but ignored by TiDB.\
instruction: please ref document: https://github.com/pingcap/docs-cn/blob/master/sql/ddl.md\
\
********** table `tlsydb`.`model_has_roles` **********\
statement: CREATE TABLE `model_has_roles` (\
  `role_id` int(10) unsigned NOT NULL,\
  `model_type` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,\
  `model_id` bigint(20) unsigned NOT NULL,\
  PRIMARY KEY (`role_id`,`model_id`,`model_type`),\
  KEY `model_has_roles_model_id_model_type_index` (`model_id`,`model_type`),\
  CONSTRAINT `model_has_roles_role_id_foreign` FOREIGN KEY (`role_id`) REFERENCES `roles` (`id`) ON DELETE CASCADE\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci\
---------- warning messages ----------\
information: Foreign Key model_has_roles_role_id_foreign is parsed but ignored by TiDB.\
instruction: please ref document: https://github.com/pingcap/docs-cn/blob/master/sql/ddl.md\
\
********** table `tlsydb`.`admin_password_resets` **********\
statement: CREATE TABLE `admin_password_resets` (\
  `email` varchar(191) NOT NULL,\
  `token` varchar(191) NOT NULL,\
  `created_at` timestamp NULL DEFAULT NULL,\
  KEY `admin_password_resets_email_index` (`email`)\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4\
---------- error messages ----------\
information: primary/unique key does not exist\
instruction: please set primary/unique key for the table\
\
********** table `tlsydb`.`password_resets` **********\
statement: CREATE TABLE `password_resets` (\
  `email` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,\
  `token` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,\
  `created_at` timestamp NULL DEFAULT NULL,\
  KEY `password_resets_email_index` (`email`)\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci\
---------- error messages ----------\
information: primary/unique key does not exist\
instruction: please set primary/unique key for the table\
\
********** table `tlsydb`.`model_has_permissions` **********\
statement: CREATE TABLE `model_has_permissions` (\
  `permission_id` int(10) unsigned NOT NULL,\
  `model_type` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,\
  `model_id` bigint(20) unsigned NOT NULL,\
  PRIMARY KEY (`permission_id`,`model_id`,`model_type`),\
  KEY `model_has_permissions_model_id_model_type_index` (`model_id`,`model_type`),\
  CONSTRAINT `model_has_permissions_permission_id_foreign` FOREIGN KEY (`permission_id`) REFERENCES `permissions` (`id`) ON DELETE CASCADE\
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci\
---------- warning messages ----------\
information: Foreign Key model_has_permissions_permission_id_foreign is parsed but ignored by TiDB.\
instruction: please ref document: https://github.com/pingcap/docs-cn/blob/master/sql/ddl.md\
\
",

提供下 dm 版本和当前 souce 源的数量,dm-worker 的数量

task 文件提供下。
给下表 tlsydb.admin_activations 的表结构看下。这个检查表结构兼容性的操作是先于数据同步的

谢谢,问题已解决,是一个task只能由一个worker执行,两个是一对一关系

:call_me_hand:

此话题已在最后回复的 1 分钟后被自动关闭。不再允许新回复。