kettle操作phoenix,强行中断造成死锁

来源:转载

######mysql-phoenix数据量太大且列很多的时候,速度很慢,如果中断kettle任务的话,会造成kettle资源库锁死。 Couldn't execute SQL: LOCK TABLES R_CLUSTER WRITE, R_CLUSTER_SLAVE WRITE, R_CONDITION WRITE, R_DATABASE WRITE, R_DATABASE_ATTRIBUTE WRITE, R_DATABASE_CONTYPE WRITE, R_DATABASE_TYPE WRITE, R_DEPENDENCY WRITE, R_DIRECTORY WRITE, R_JOB WRITE, R_JOBENTRY WRITE, R_JOBENTRY_ATTRIBUTE WRITE, R_JOBENTRY_COPY WRITE, R_JOBENTRY_DATABASE WRITE, R_JOBENTRY_TYPE WRITE, R_JOB_ATTRIBUTE WRITE, R_JOB_HOP WRITE, R_JOB_LOCK WRITE, R_JOB_NOTE WRITE, R_LOG WRITE, R_LOGLEVEL WRITE, R_NOTE WRITE, R_PARTITION WRITE, R_PARTITION_SCHEMA WRITE, R_REPOSITORY_LOG WRITE, R_SLAVE WRITE, R_STEP WRITE, R_STEP_ATTRIBUTE WRITE, R_STEP_DATABASE WRITE, R_STEP_TYPE WRITE, R_TRANSFORMATION WRITE, R_TRANS_ATTRIBUTE WRITE, R_TRANS_CLUSTER WRITE, R_TRANS_HOP WRITE, R_TRANS_LOCK WRITE, R_TRANS_NOTE WRITE, R_TRANS_PARTITION_SCHEMA WRITE, R_TRANS_SLAVE WRITE, R_TRANS_STEP_CONDITION WRITE, R_USER WRITE, R_VALUE WRITE, R_VERSION WRITE, R_NAMESPACE WRITE, R_ELEMENT_TYPE WRITE, R_ELEMENT WRITE, R_ELEMENT_ATTRIBUTE WRITE Lock wait timeout exceeded; try restarting transaction 解决:删除原有kettle脚本重新建或另存为

分享给朋友:
您可能感兴趣的文章:
随机阅读: