You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "XiaoXiang Yu (JIRA)" <ji...@apache.org> on 2019/06/12 03:26:00 UTC
[jira] [Commented] (KYLIN-3954) kylin one instance log
:executablePO is null
[ https://issues.apache.org/jira/browse/KYLIN-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861716#comment-16861716 ]
XiaoXiang Yu commented on KYLIN-3954:
-------------------------------------
Hi, it looks like it is caused by some broken metadata.
> kylin one instance log :executablePO is null
> --------------------------------------------
>
> Key: KYLIN-3954
> URL: https://issues.apache.org/jira/browse/KYLIN-3954
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
> Affects Versions: v2.6.1
> Environment: cdh57-hadoop
> Reporter: leh
> Priority: Major
> Labels: starter
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> in kylin instance, the kylin.log print mang WARN log, like this:
> ------
> 2019-04-12 11:56:38,636 WARN [http-bio-8070-exec-12] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:38,641 WARN [http-bio-8070-exec-11] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:38,786 WARN [http-bio-8070-exec-10] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:38,787 WARN [http-bio-8070-exec-4] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:38,937 WARN [http-bio-8070-exec-15] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:38,937 WARN [http-bio-8070-exec-14] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,088 WARN [http-bio-8070-exec-9] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,088 WARN [http-bio-8070-exec-13] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,238 WARN [http-bio-8070-exec-5] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,238 WARN [http-bio-8070-exec-6] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,398 WARN [http-bio-8070-exec-8] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,398 WARN [http-bio-8070-exec-3] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,549 WARN [http-bio-8070-exec-2] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,549 WARN [http-bio-8070-exec-7] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,699 WARN [http-bio-8070-exec-1] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,702 WARN [http-bio-8070-exec-12] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,851 WARN [http-bio-8070-exec-11] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:39,852 WARN [http-bio-8070-exec-10] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,001 WARN [http-bio-8070-exec-4] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,003 WARN [http-bio-8070-exec-15] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,152 WARN [http-bio-8070-exec-14] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,157 WARN [http-bio-8070-exec-9] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,305 WARN [http-bio-8070-exec-13] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,308 WARN [http-bio-8070-exec-5] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,455 WARN [http-bio-8070-exec-6] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,458 WARN [http-bio-8070-exec-8] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,605 WARN [http-bio-8070-exec-3] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,609 WARN [http-bio-8070-exec-2] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,754 WARN [http-bio-8070-exec-7] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,759 WARN [http-bio-8070-exec-1] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,903 WARN [http-bio-8070-exec-12] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:40,911 WARN [http-bio-8070-exec-11] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:41,053 WARN [http-bio-8070-exec-10] execution.ExecutableManager:563 : executablePO is null
> 2019-04-12 11:56:41,061 WARN [http-bio-8070-exec-4] execution.ExecutableManager:563 : executablePO is null
> ---------
> what's wrong? how to resolve it? so many WARN infos print frequently.
> memo:
> cluster is three kylin instance, two instance is "kylin.server.mode=all" ,the last one is query.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)